top of page

Drone surveying is becoming established as a method that makes it easy to capture large areas in a short time and aids efficiency on civil engineering and construction sites. It can be carried out with fewer people than before, and a major appeal is its wide applicability to tasks such as site condition assessment, as‑built verification, earthwork volume measurement, and progress sharing. At the same time, in actual fieldwork there are many cases where assuming “just flying it is enough” leads to unexpected failures.


Especially for those responsible for moving operations in-house and for operational staff who have only been partially involved so far, it is important to understand in advance what can lead to failure. Failures in drone surveying are not caused solely by piloting errors. They arise from the overlap of multiple factors — insufficient checks during the planning phase, overlooking site conditions, lax camera/shooting settings, inadequate establishment of reference/control points, judgment errors during processing steps, and so on. What makes this particularly troublesome is that problems often go unnoticed when the flight is completed on site and only surface later during post-processing or result verification.


In other words, in drone surveying what you really need to avoid is not just the flashy failures that are obvious on the spot. It is the quiet failures—those that later require re-shooting, cannot be used as comparative data, or cannot withstand explanations to clients or within the company—that become a burden in practice, because they gradually take effect in the form of schedule delays, the need to secure additional personnel, revisits, redoing neighborhood coordination, and a loss of confidence in the deliverables.


This article organizes nine common failures encountered in drone surveying in the field and explains, from a practical perspective, why each occurs and how to prevent them. To be useful both for those about to introduce drone surveying and for those already operating it, we address typical oversights as specifically as possible. As a way of thinking to reduce reshoots and rework on site and to turn survey data into usable deliverables, please read through to the end.


Table of Contents

• Reasons why drone surveying is prone to failure

• Failure example 1: Entering the site without a plan and lacking sufficient coverage for shooting

• Failure case 2: Underestimating weather and wind, resulting in reduced image quality and safety

• Failure case 3: Processing accuracy degrades because altitude and overlap rate settings do not match

• Failure case 4: An ambiguous approach to control points and georeferencing causes unstable coordinates

• Failure Case 5: Overlooking obstacles and terrain changes causes unstable flight

• Failure Example 6: Neglecting on-site checks, requiring reshooting

• Failure Example 7: Being satisfied with only creating point clouds and orthophotos and not producing usable deliverables.

• Failure Example 8 Insufficient sharing among stakeholders causes on-site operations to stop

• Failure example 9: Postponing securing the accuracy needed for setting out and as-built verification

• Summary


Reasons Why Drone Surveys Often Fail

The reason drone surveying fails so often is that the work looks deceptively simple. As aircraft performance has improved and automated flight has become common, even those with little experience can carry out basic flights. However, to produce valid surveying results, the planning before and after the flight is more important than the flight itself. If it remains unclear where, for what purpose, with what level of precision, and into what deliverables the survey will be converted, the image capture itself may succeed but the operation will still be a failure.


Also, drone surveying is a task made up of multiple consecutive processes. Site reconnaissance, flight planning, safety checks, photography, securing control points, data organization, data processing and analysis, verification of results, and sharing and utilization—if even one of these is omitted, the overall quality suffers. On site, teams are often pressed for time, and because of changing weather and personnel constraints, attention tends to focus only on the flight at hand. As a result, after returning to the office problems occur such as "the required locations were not captured," "coordinates don't match," "data cannot be compared," and "it cannot be used for explanations."


Furthermore, the conditions required for drone surveying vary depending on its purpose. Whether it is for assessing current site conditions, as-built management, earthwork volume calculation, or comparison with design, the necessary capture and processing conditions change. If the settings do not match the intended purpose, the data may look good visually but be unusable. To avoid failures, you need not only good piloting skills but also the ability to relate the surveying objectives to the site conditions.


Failure Example 1 Entering the site without a plan and ending up with insufficient shooting coverage

One of the most common initial mistakes is insufficient planning before shooting. If you roughly decide the coverage after arriving on site and hastily fly only over the spots that catch your eye, you may later find that the coverage is insufficient. For example, at a land-development site you might have omitted the slope crest or slope toe even though they should have been included, or you may have captured only the target area when you should have recorded the access road and surrounding structures, making comparisons or explanations in later stages difficult.


One reason this failure occurs is that the area required on site is viewed only in two dimensions. In drone surveying, not only the main subject but also the connections with the surrounding area are important. There is surprisingly much information that will be needed later to explain the situation—such as areas near boundaries, access points, temporary structures, slopes, drainage routes, and elevation differences with adjacent land. However, on site there is a tendency to assume "for now, it's enough to cover only the central area," and that laxity leads to revisits.


To prevent this, it's important to clarify the purpose before flight and to distinguish between the minimum required imaging area and an area that includes some margin. In practice, it's safer to include a bit more of the surroundings rather than framing exactly the required area. You can crop later, but you can't add what wasn't captured. Especially when using the images for current-condition records or design comparisons, it's important to capture not only the object itself but also the context in front, behind, left, and right.


Also, attention must be paid to discrepancies between preliminary drawings or existing documents and the actual site. It is not uncommon for the area you reviewed on paper to differ from actual site conditions. Landing zones, access restrictions, the placement of heavy machinery, and material storage areas can prevent you from taking the flight paths you had expected. Therefore, rather than flying as soon as you arrive, it is effective practice to walk the site once to confirm conditions and to overlay and organize the required coverage with the flyable area. Lax planning will inevitably surface at the end as missed shots.


Failure Example 2: Underestimating Weather and Wind Leads to Degraded Image Quality and Reduced Safety

In drone surveying, you need to assess not only whether the drone can fly but also whether conditions are suitable for taking measurements. A common mistake is underestimating the weather and wind. For example, even if it isn’t raining, situations such as intermittent strong winds, fast-moving winds at altitude, muddy ground, or rapid cloud movement causing extreme changes in light and shadow can significantly degrade image quality and safety.


When the wind is strong, the aircraft must make more attitude corrections, which affects stability during shutter release. As a result, images may show slight motion blur or it may become difficult to maintain consistent overlap, leading to poor stitching in post-processing. Also, if the wind pushes the aircraft so it cannot maintain planned speeds or routes, battery consumption becomes harder to predict and safety margins shrink. Even if the flight itself is completed, if data quality is insufficient the survey is considered a failure.


In addition, at sites just after rain or immediately after overcast conditions, the effects of ground reflections and puddles cannot be ignored. Wet road surfaces and bodies of water make it difficult to extract features in images, and in some locations they degrade processing accuracy. Conversely, even in clear weather, if shadows become too deep depending on the time of day, information around slopes and structures can become hard to see. In other words, weather conditions are directly linked not only to safety but also to the quality of results.


To prevent this, you should have multiple pieces of information to base your on-site decisions on the day. Look at not only the wind speed figures but also how the wind is blowing at the site, eddies caused by the terrain, differences between upper air and the ground, how shadows form, and the dryness of the ground surface, and evaluate them comprehensively. Rather than forcing a flight on that day, shifting to a time with better conditions can ultimately be more efficient. At the site, there is a mindset of "we already made the trip today, so we should do it today," but that judgment is the most dangerous. Cancellation or postponement are also correct decisions to ensure quality and are important choices to prevent failures in advance.


Failure Case 3: Mismatch Between Altitude and Overlap Settings Causes Processing Accuracy to Deteriorate

A very common cause of poor accuracy in drone surveying is incorrect settings for flight altitude and image overlap. On site, with the intention of shortening work time, operators may fly too high or space capture intervals too widely. While this does make it easier to cover a large area in a short time, if the required ground resolution or image overlap is insufficient, the stability of processing falls off sharply.


If the altitude is too high, the legibility of fine ground features decreases. Edges of road shoulders, cracks, boundary markers, narrow gutters, outlines of temporary materials, and other information you want to verify on site tend to become blurred. Moreover, in areas with large terrain changes, the appearance can vary by location even with the same altitude setting, making it difficult to maintain uniform quality. On the other hand, if the altitude is too low, the number of images increases, which can lead to excessive processing time and operational burden. The important point is not a simple matter of lower being better or higher being worse, but to consider the optimal setting according to the objective.


The same applies to overlap rate. If front-to-back and side-to-side overlap is insufficient, the correspondences between images become weak, making distortions and gaps in the processing results more likely. Especially on sites with monotonous ground surfaces—grass, uniformly prepared ground under construction, or many paved surfaces—there are few feature points, so you need to allow extra overlap. Even if you feel reassured by the configured values alone, in practice overlap can drop below expectations due to wind or speed variations.


To prevent this failure, it is important to determine settings by working backwards from the deliverables required for each purpose. The conditions differ between current-condition checks and as-built comparisons, and the required density also varies between earthwork volume calculations and aerial overview images for presentation. Furthermore, appropriate settings change depending on site topography, vegetation, and the presence or absence of structures. You need an approach that plans not only to shorten flight time but also to ensure processing stability. Fine-tuning capture conditions may seem tedious, but skipping this step will cost many times more time in downstream processes.


Failure Case 4: An ambiguous approach to control points and calibration causes unstable coordinates

In drone surveying, even if visually appealing images and point clouds are obtained, they become difficult to use in practice if the coordinates are not stable. A common issue here is a lack of understanding of control points and georeferencing. At some sites, teams rely too heavily on the aircraft's positioning performance and omit necessary checks and reinforcements. As a result, positional and vertical shifts may be discovered later, making the data unusable for comparisons or as-built verification.


The scary thing about this failure is that it’s hard to notice at a glance. Both the orthophotos and the point clouds can look plausible, so on site you get the impression it succeeded. However, when you overlay them with existing drawings, compare them with data acquired on different days, check cross-sections, or perform quantity calculations, the misalignments gradually surface. And if the problem is discovered only after you’ve returned to the office, it becomes difficult to isolate the cause and to decide whether to re-acquire the data.


Many of the causes are that the approach to coordinate management appropriate to the intended use has not been clarified. Whether it is a simple record, a comparison with the design, or capturing changes across multiple time points, the consistency required differs. Nevertheless, operating with the same mindset every time can lead to insufficient accuracy when it is needed. In addition, control points may be unevenly placed, markers may have poor visibility, or an appropriate number and placement may not have been secured for site conditions.


To prevent this, clarify before the flight "what you will overlay this data on" and "what future comparisons it will be used for." If the data will be used for comparisons, a workflow that only works on the day of the flight is not sufficient. It is important to be able to handle it consistently under the same standards over time. The more advanced the application—such as positioning, as-built checks, earthwork volumes, and construction records—the less you can afford to neglect the thinking behind the standards. Positioning and calibration are unglamorous preparations, but if they remain vague, no matter how high-quality the images you capture, the overall reliability of the results will not increase.


Failure Example 5: Overlooking obstacles and terrain changes causes unstable flight

On-site flight incidents often occur not only because of inexperienced aircraft handling but also due to insufficient preflight site assessment. Particularly common are cases where a flight is initiated without adequately checking for obstacles or terrain changes. Power transmission facilities, trees, temporary structures, cranes, slopes, level differences, embankments, and valley-like terrain can have a major impact on flight routes, communications, and visibility.


Even sites that look safe on a plan view can have many blind spots when you actually stand there. The aircraft can easily end up behind standing trees, on a slope it’s easy to lose your sense of altitude, it can be difficult to visually monitor things over temporary fencing, and winds aloft can be turbulent in valleys—there are many conditions that can only be discovered on site. If you overlook these conditions, you may be forced to change your flight route on the spot, resulting in missed shots or insufficient overlap. It is a common mistake to discover, after diverting for safety, that the necessary data was not collected.


Also, the selection of takeoff and landing sites must not be overlooked. In conditions such as soft ground, dusty surroundings, frequent movement of work vehicles, or proximity to third-party traffic routes, preparation and recovery can be more dangerous than the flight itself. If you focus so much on surveying that you lose sight of what’s happening around you, the overall safety of the site will be reduced.


As a preventive measure, do not make the pre-flight on-site check merely a formality. Rather than just looking over the coverage area, anticipate where the drone will become hard to see, where the wind will change, how to plan escape routes, and even where maintaining altitude will become difficult. Also, it is reassuring to have alternative flight/filming routes instead of a single route in case conditions deteriorate. In drone surveying, a ground-based perspective for interpreting the site is indispensable in addition to the aerial viewpoint.


Failure Example 6: Neglecting on-site verification, requiring a reshoot

One of the most frustrating mistakes in practical work is having to reshoot because you skipped the on-site check after the flight. On site, once the flight is over you tend to relax and want to pack up and leave. However, what really matters in surveying is confirming on the spot that the data you collected is sufficient for its intended purpose. If you neglect this, you may discover after returning to the office that there are gaps or missing data, blur, insufficient coverage, insufficient overlap, or coordinate inconsistencies, and a revisit will be necessary.


This failure is more likely to occur at busy sites. In situations where the next work is tightly scheduled, sunset is approaching, or stakeholders have limited time to be present, verification steps tend to be postponed. However, if skipping a few minutes of on-site checks means assembling personnel and equipment to return to the site the following week, the burden is much greater.


What you need to check is not simply whether the number of images is sufficient. A practical perspective is required: whether the target coverage is adequate, whether there are missing parts at the edges, whether shadows or reflections are problematic, whether there are too many areas with few distinguishing features, whether the necessary ground features are legible, and whether the density appears sufficient for the intended use. Even if it is difficult to wait on site for point clouds or orthomosaics to be completed, you can still perform a minimum quality check.


To prevent this, formalize a pre-departure check as a standard operating procedure. Rather than relying on the individual’s experience, put in place a system that ensures checks are made from the same perspective every time, which reduces omissions. Especially when multiple people are working together, it is important to make clear “who checks what before packing up.” Failures in drone surveying often arise not during flight but from lapses in attention just before packing up.


Failure Example 7: Being satisfied with merely creating point clouds and orthomosaics, resulting in unusable deliverables

In drone surveying, it can feel like the job is done once point clouds and orthophotos have been generated. However, in practice the real work begins from that point onward. A common failure here is that creating the data itself becomes the goal, and it is not translated into deliverables that can be used on site. Even with a clean point cloud, its practical value is limited if it is not tied to design comparisons, quantity verification, report materials, shared drawings, cross-section checks, and so on.


For example, it is not uncommon to encounter cases where a point cloud of the existing conditions exists but is not organized in the required coordinate system and therefore cannot be overlaid with other data; where orthophotos exist but are not shared in a format that stakeholders can easily work with; or where people want to use the data to check cross-sections but the approach to defining the check locations has not been organized. Even if surveyors understand what everything means, if construction managers and designers find it difficult to use, it will not be utilized across the site.


At the root of this failure is a lack of consideration for the users of the deliverables. The results of drone surveying are not just for surveyors. Various stakeholders are involved, including construction personnel, managers, partner companies, and clients. If you produce data without thinking about who will look at what and in which situations it will be needed, the data may exist but it will not be put to use.


To prevent this, define the outputs before acquisition. If you are assessing current conditions, decide what to show; for as-built verification, determine where to compare; for earthwork quantities, establish the range over which to calculate; for reporting, decide in what format to share. Doing so clarifies the required capture and processing conditions. Drone surveying is not only a data acquisition technology but also an information-preparation task that supports on-site decision-making. A mindset of not stopping at merely producing the deliverables is the key to avoiding failure.


Failure Case 8: Insufficient Stakeholder Communication Halts On-site Operations

Drone survey results are not something that can be completed by a single person. Nevertheless, operations often stop due to insufficient sharing among stakeholders. For example, the field personnel may think they have captured the data but it hasn’t been shared with the construction team; it was shared but cannot be opened due to size or format issues; it’s unclear which file is the latest; or the area covered hasn’t been communicated. When this happens, the data that was painstakingly acquired goes unused, and the site reverts to the conventional methods of verification.


Also, insufficient information sharing before shooting can cause failures. If coordination with nearby work, access restrictions, heavy equipment movement, responses to third parties, and notification of the site supervisor are inadequate, tasks may overlap the scheduled flight time, making it difficult to ensure safety. Even if only the surveying personnel are prepared, things will not proceed smoothly without understanding across the entire site.


When sharing results, the important thing is not simply sending files but conveying how to interpret and use them. Only when recipients understand which parts were updated, what point in time the data represents, what it can be used for, and where to pay attention will it be used for on-site decision-making. Because the amount of information required varies depending on the recipient's position, organizing information solely according to the surveyor's logic makes it difficult to communicate.


To prevent this, make sharing before and after flights a standard part of the workflow. Before flight, share the objectives and constraints; after flight, organize and communicate the meaning of the results and how they should be used. Especially in ongoing operations, simply aligning naming rules, storage locations, update timestamps, and the approach to version control greatly reduces confusion. Failures in drone surveying are often not caused by the technology itself but by insufficient information transfer.


Failure Example 9: Postponing Ensuring the Accuracy Required for Setting Out and As-Built Verification

Lastly, the most fundamental failure I want to point out is this: postponing the assurance of the necessary accuracy for practical applications where precision matters—such as setting out or as-built verification. On site, people tend to start by "just taking pictures," but the more demanding the application, the less viable it is to rely solely on the ease of shooting.


For example, in situations where you want to compare with the design, accurately confirm the construction area, grasp trends in the as-built condition early, or consider layout based on point clouds, consistency is more important than the appearance of the data. If this remains ambiguous, slight misalignments will become noticeable when you overlay them later, and ultimately the data will be treated as “usable only as a reference.” Introducing drone surveying but finding it unusable for the core aspects is a major missed opportunity for the site.


This failure happens because the common early-stage mindset of "let’s start with recording only" is carried straight into tasks that demand high accuracy. Operations that were acceptable for recording purposes are not necessarily suitable for as-built verification or comparative uses. When the intended use changes, the necessary preparations, positioning management, verification methods, and the depth of results confirmation must also change.


To prevent this, it is effective to view the purpose of surveying in stages. Depending on whether it is merely a record, for management, or for decision-making, consider the required quality separately. In operations involving positions, it is important to be mindful of stably linking the coordinates and reference points used on site. In such situations, systems that make it easier to handle high-precision position information in combination with smartphones are also effective. By thinking consistently—from on-site verification and recording, to sharing target locations and bridging to subsequent processes—the value of drone surveying is greatly enhanced.


Summary

Failures in drone surveying do not occur only at special sites. Rather, the more routine the site, the more likely failures are to occur because basic checks are skipped amid familiarity and busyness. Lack of planning, poor judgment of weather conditions, incorrect settings, unclear control-point management, overlooking obstacles, insufficient on-site verification, inadequate planning for utilizing results, poor information sharing, and insufficient understanding of accuracy requirements. None of these are dramatic, but they are very common failures in practice.


The important thing is to regard drone surveying not as a flight operation but as a business process that includes using the deliverables. Rather than focusing on whether the flight was completed, if you look from the perspective of whether the results can be used for on-site decision-making, for comparisons, for explanations, or whether they connect to the next process, the seeds of failure become apparent at a much earlier stage. Conversely, simply being rigorous about pre-planning, on-site checks, organizing standards, and devising methods for sharing can prevent a great deal of rework.


If you want to make drone surveying more useful on site going forward, it is important not to limit the process to aerial imaging alone but to systematize it to include on-the-ground position checks and data integration. In particular, linking information captured on site with high-precision positional data and making it usable for stakeholders without confusion will become increasingly important. When planning such operations, combining technologies like LRTK, an iPhone-mounted GNSS high-precision positioning device, makes it easier to improve the accuracy and speed of on-site position checks, recording, and sharing. To reduce failures in drone surveying and ensure that acquired data is effectively used in practice, having a perspective that connects aerial and ground information will make a major difference on future sites.


Next Steps:
Explore LRTK Products & Workflows

LRTK helps professionals capture absolute coordinates, create georeferenced point clouds, and streamline surveying and construction workflows. Explore the products below, or contact us for a demo, pricing, or implementation support.

LRTK supercharges field accuracy and efficiency

​

The LRTK series delivers high-precision GNSS positioning for construction, civil engineering, and surveying, enabling significant reductions in work time and major gains in productivity. It makes it easy to handle everything from design surveys and point-cloud scanning to AR, 3D construction, as-built management, and infrastructure inspection.

bottom of page