A successful aerial data mission begins before the aircraft ever leaves the ground.

​

The more we understand about the project, the site, and the intended use of the data, the better we can design the mission around what actually needs to be accomplished.

​

That does not mean a client needs to know exactly which photogrammetry product to request before contacting us.

​

It means we need to understand the question.

What are you trying to document, measure, compare, preserve, or understand?

​

That answer shapes everything that follows.

Start with the purpose of the project. Are you documenting existing conditions? Tracking change over time? Creating a construction baseline? Examining terrain? Preserving a record before work begins? Building a three-dimensional representation of the site? Supporting another professional workflow?

​

The objective matters because different questions require different acquisition strategies.

​

We also need to understand exactly where the project is located and what area needs to be covered. An address is useful, but site plans, KML or KMZ files, boundary drawings, coordinates, or other location information can help define the mission much more clearly. If there are areas that should not be included, restricted locations, neighboring properties, sensitive areas, or operational boundaries, those should be identified before the flight.

​

Deliverables should be discussed early as well, but they should follow the purpose of the mission. Depending on the project, that may include an orthomosaic, three-dimensional model, point cloud, surface model, source imagery, georeferenced files, or other project-specific products.

​

If you already know what you need, tell us.

​

If you do not, tell us what you are trying to accomplish and we can help determine what type of deliverable makes sense.

​

Timing matters too. Some projects require a single mission. Others become more valuable when the site is documented repeatedly over time. Weekly, monthly, milestone-based, or event-driven flights may be appropriate depending on the project.

​

If repeatability matters, we want to know that at the beginning because consistency in coverage, altitude, control, processing, and documentation may become part of the mission itself.

​

Site access and operating conditions are another important part of planning. We need to know how to enter the property, where we can safely operate, whether there are security procedures, personal protective equipment requirements, restricted areas, active construction, cranes, power lines, equipment movement, blasting, wildlife concerns, or other site hazards that could affect the flight.

​

Airspace and surrounding aviation activity are evaluated as part of our planning, but any site-specific information you have can be useful.

​

Some projects also require coordination with other professionals. That may include surveyors, engineers, airport personnel, contractors, environmental specialists, or other stakeholders whose work affects how the aerial data should be collected.

​

If ground control, specific coordinate systems, documented accuracy, or other technical requirements are part of the project, those expectations should be identified before the mission is designed.

​

The goal is not to collect as much information as possible.

​

The goal is to collect the right information.

​

Aerial data becomes more useful when the mission is designed around a clear purpose, the coverage is defined, the intended deliverables are understood, and the conditions surrounding the work are known before flight day.

​

The better we understand the project before takeoff, the better chance we have of returning with the answer the mission was designed to produce.