Drone Building Inspection: From Flight Plan to Final Report

On This Page

• Define the inspection before booking the flight
• Turn the building information into a flight plan
• Match image detail and thermal conditions to the question
• Check coverage before leaving the site
• Build findings that lead back to the original evidence
• Specify a report the maintenance team can use
• Questions to settle with the provider

Define the inspection before booking the flight

Write the assignment around a decision: locating visible roof damage before a contractor visit, documenting facade condition for maintenance planning, or identifying roof areas that warrant moisture verification. Give the inspector the building address, drawings where available, roof construction, known leaks, previous repairs, and the areas that matter most. Identify who will interpret the results and who can authorize follow-up access.

Keep three services distinct in the proposal:

• Capture: obtaining and organizing images of specified surfaces.
• Assessment: interpreting those images in the context of the building and its history.
• Confirmation: investigating a suspected condition through appropriate closer examination or testing.

New York City's Department of Buildings made this distinction in its Using Drones to Conduct Facade Inspections study: visual data needs professional analysis, and photographs cannot perform physical examination such as sounding or probing. Treat that report as a study of inspection limitations, rather than current permission to fly in New York City. Read the DOB study.

For a broader explanation of what photographs, measurements, and interpretation establish, see our six levels of drone-inspection evidence.

Agree on exclusions before mobilization. These might include concealed fixings, roof areas underneath equipment, interiors, or surfaces that cannot be photographed safely. An exclusion should identify the affected location and its consequence for the owner's decision.

Turn the building information into a flight plan

Use a roof plan and elevation drawings to divide the building into named inspection zones. Where reliable drawings are unavailable, agree on a simple reference system: building, compass-facing elevation, floor band, and bay. Keep the same identifiers in the image folders, findings register, and final report.

Plan the roof and facades separately. Looking downward at a roof does not establish coverage of vertical walls, recesses, parapet faces, or the underside of projections. For each zone, specify an overview for orientation and the detail views needed to answer the inspection question. Additional angles should address an identified blind spot, rather than simply increase the photograph count.

The site review should establish launch and landing areas, occupied entrances, pedestrian routes, neighboring property, obstructions, and where the pilot can maintain the required view of the aircraft. Agree with the building manager how access will be controlled and what happens if the planned area cannot be kept clear.

For U.S. commercial work with a small drone, the FAA's Part 107 pathway covers pilot certification and operating requirements. Flights at night or over people and moving vehicles must meet the applicable conditions; they are not blanket permissions. Have the operator identify the airspace authorization or waiver needed for the actual mission before confirming the date. FAA guidance for commercial operators provides the starting point. Building access permission and local site restrictions also need to be settled for the particular location.

Ask the provider to include a weather fallback and a method for recording surfaces left uninspected. If the intended view cannot be obtained safely, the report should identify the gap and propose another access method.

Match image detail and thermal conditions to the question

Visible-light images: specify the feature that must be recognizable

Megapixels alone do not describe inspection detail. NIST's target-size guidance explains that recognizable detail depends on how much of the camera's field of view the target occupies, which changes with target size, distance, and optics. Its guidance concerns video quality, not a building-defect detection standard. NIST's target-size explanation is useful when reviewing a proposed camera setup.

Ask for a representative image of the relevant material and feature, captured at the planned working distance. Review the original file at full resolution. Confirm that focus, exposure, viewing angle, and motion blur allow the intended observation. A sample that can show missing cladding may still be unsuitable for assessing a fine joint opening.

As an illustrative calculation, suppose a square-on image covers a wall width of 12 metres across 6,000 pixels. The nominal sampling is 12,000 millimetres divided by 6,000 pixels, or 2 millimetres per pixel. A 4-millimetre feature would span only two pixels under those simplified assumptions. This is a sampling calculation, not a demonstrated detection limit or a measurement-accuracy claim. Require an appropriate check before accepting numerical crack widths or dimensions.

Thermal images: agree on the investigation method first

For wet roof insulation, ASTM C1153-23 describes a specific application: nighttime infrared inspection of roofing systems with insulation above the deck and in contact with the waterproofing. Its published scope covers aerial and ground inspection, weather and construction conditions, and invasive verification. It does not determine the moisture's cause or entry point. ASTM's public scope and significance statement explains these boundaries.

The buyer's implication is to establish the roof assembly and verification method before commissioning a thermal survey. Do not assume one nighttime roof procedure answers an insulation or air-leakage question on every facade. Ask the thermographer which method fits the actual assembly and which site conditions would make the results inconclusive.

Temperature interpretation also needs more than a color palette. FLIR's measurement documentation identifies emissivity, reflected temperature, distance, atmospheric temperature, and humidity as relevant inputs. Emissivity describes how effectively a material emits thermal radiation; reflected surroundings can also contribute to what the camera receives. FLIR's temperature-measurement documentation explains those settings.

Request the original thermal data, corresponding visible images, acquisition conditions, and the settings used for reported temperatures. Label an unexplained pattern as a thermal anomaly until the inspection method supports a stronger conclusion.

Check coverage before leaving the site

Make a coverage review part of the field assignment. Compare each zone with the planned views, inspect representative original files, and list missing or unusable areas while a return flight may still be practical. Keep inaccessible surfaces separate from surfaces photographed without a visible finding.

Coverage must have a defined denominator. Consider an illustrative building with 40 equal-area facade zones. If 36 zones meet the agreed image requirements and four remain obscured, usable zone coverage is 36 divided by 40, or 90%. That figure does not mean 90% of defects were detected, and it does not mean the building passed an inspection.

If the zones differ in size, describe the result as a zone count or calculate coverage from their areas. Avoid presenting the percentage of completed flight waypoints as the percentage of building surface inspected. For priority locations, require individual status even when total coverage is high: one missing view above a busy entrance can matter more than several complete views elsewhere.

The field handover should identify whether each gap requires a return flight, a different viewpoint, physical access, or an agreed limitation. Include who decides whether the remaining gap is acceptable for the intended use.

Build findings that lead back to the original evidence

Organize the capture before interpreting it. Preserve original filenames and timestamps, associate files with the correct building zones, and keep marked-up copies separate from originals. A reviewer should be able to move from a finding to an overview, then to the original detailed image without guessing which wall is shown.

A practical finding record contains:

1. A unique finding ID and building location.
2. A short observation describing what is visible.
3. An overview, detail image, and original file reference.
4. The interpretation, its uncertainty, and any required confirmation.
5. A recommended next action, responsible role, and review date where appropriate.

For example, a hypothetical entry could read: “East elevation, level 3, bay E07: apparent joint opening beside window head. Refer to overview E03 and detail E07-014. Arrange closer examination to establish joint condition and repair needs.” This does not assign a cause or measured width that the photograph has not established.

A model can help locate findings, but the source images must remain accessible. DroneDeploy's facade inspection documentation illustrates this workflow: users open camera-position images, add field notes to source imagery, and include those notes in a report. It also states that export resolution is limited to the current browser viewport. Verify detail in the delivered files, especially when the owner will work from a PDF. A visually convincing model is not itself proof that its dimensions are accurate. DroneDeploy's facade reporting documentation describes the example and its export limitation.

If automated defect detection is included, require review of the proposed findings and a stated treatment of unflagged images. Ask how the provider checks missed defects and false alarms on the relevant surfaces. A count of software annotations is not a building condition rating.

Specify a report the maintenance team can use

Use the following proposed schedule to make competing scopes comparable. These are editorial purchasing recommendations, informed by the inspection and reporting sources above; they are not a universal inspection standard.

Set the delivery format and access terms before signing. Request a downloadable report and findings register, establish rights to retain the original images, and define how long hosted data remains available. Agree who can access building imagery and how unrelated people or neighboring interiors will be handled in shared outputs.

Agree on an immediate contact route for a suspected urgent hazard; notification should not wait for the finished PDF. Use the handover meeting to resolve remaining questions about findings and uncovered surfaces. Distinguish the capture date from the report date so later readers know when the building was observed.

For repeat inspections, retain the zone names and finding IDs. Ask the next provider to reproduce useful viewpoints and document differences in capture conditions. An apparent change should lead back to comparable original images before it becomes a claim that deterioration has progressed.

Questions to settle with the provider

Before accepting a proposal, get specific answers to these questions:

• Who is responsible for flight operations, building-condition interpretation, and any formal inspection sign-off?
• Which roof and facade surfaces are included, and how will incomplete coverage be reported?
• What sample demonstrates the detail needed for this assignment?
• What physical follow-up is included, separately priced, or outside the service?
• How will thermal findings or claimed measurements be checked?
• Do the fees include site coordination, processing, interpretation, report revisions, and a return visit if capture quality fails the agreed requirements?
• Which files will the owner retain after any hosted access ends?

Choose the scope that carries the maintenance question all the way to a usable answer. For routine visual documentation, that may be a well-organized photo survey with located observations. For suspected hidden deterioration or moisture, it may require a combined aerial survey and targeted physical investigation. Agree on those responsibilities and the sample deliverables before the flight is booked.

Source notes

• NYC Department of Buildings: Using Drones to Conduct Facade Inspections. Government study explaining the distinction between aerial visual data, professional assessment, and physical examination; not used as current local flight authorization.
• FAA: Certificated Remote Pilots including Commercial Operators. Official overview of the U.S. Part 107 pathway and conditional operating permissions.
• NIST: VQiPS Target Size. Government technical guidance on target size, distance, field of view, and recognizable image detail.
• ASTM C1153-23: Location of Wet Insulation in Roofing Systems Using Infrared Imaging. Public standard scope and significance statement defining applicability and verification boundaries; the full paid standard was not used.
• FLIR: Measuring Temperatures. Manufacturer documentation explaining infrared measurement parameters and reflected radiation.
• DroneDeploy: Vertical Facade Inspections. Provider documentation illustrating source-image annotations, report generation, and an export-resolution limitation.

Last checked: September 6, 2026.