A Rigorous Process. Every Project, Every Time.

The first conversation covers your site or asset type, the deliverable you need (a report, a model, a mapping output, raw footage), the timeline, and any access constraints we should know about — permits, active operations, restricted zones, physical obstructions, or seasonal windows. This conversation shapes everything downstream. A construction site inspection has different flight pattern requirements than a crop health survey. An infrastructure inspection of a transmission corridor requires different airspace planning than a real estate aerial. We do not run a generic intake form; we ask specific questions because the answers change the plan.

Concurrent with site consultation, we conduct an initial regulatory assessment: What class of airspace covers the site? Are there controlled aerodromes within 3 nautical miles? Are there active NOTAMs or temporary flight restrictions? Are any Special Flight Operations Certificate (SFOC) considerations triggered by the scope? This assessment is completed before any proposal leaves our office. It is also how we identify any constraints that need to be flagged to the client upfront — no surprises on the day of operations.

Once scope is confirmed, we build a formal flight plan: entry and exit routes, flight altitude, pattern type (grid, orbit, linear transect), sensor settings, weather minimums, emergency landing zones, and communication protocols for the site. Flight plans are tailored to the asset — a bridge deck inspection uses a different pattern than a 500-acre field mosaic.

Where the site requires it — controlled airspace, operations near an aerodrome — we file for authorization through the appropriate Transport Canada and NAV CANADA channels before the operation date. We do not fly first and ask for forgiveness. Authorization is confirmed before mobilization.

On the day of flight operations, we conduct a fresh NOTAM review for the operational area, covering any last-minute airspace closures, TFRs, or notices that postdate the original planning cycle.

A pre-flight safety brief covers: local weather and wind, site hazards identified during planning or on arrival, emergency procedures, radio frequencies and ATC contacts where relevant, and the crew communication protocol for the operation. For multi-day engagements, this is repeated each day.

Flight paths are executed as planned, not improvised. Systematic patterns — grid, double-grid, orbit, linear transect, or point-of-interest — are chosen based on the deliverable requirement. Grid patterns for mapping and orthomosaic generation. Orbital and point-of-interest patterns for structure inspection and 3D model generation. Linear transects for corridor infrastructure like pipelines and transmission lines. Where GPS-aided autonomous flight is used, the mission is pre-programmed and verified on the ground before execution. The pilot maintains visual line of sight and full override authority throughout.

Overlap ratios, sensor settings, and image resolution are set to match the deliverable specification before the aircraft leaves the ground. These are not adjusted mid-flight based on feel — they are planned values, logged, and repeatable on follow-up visits to the same site.

During operations, site conditions — wind speed and direction, temperature, visibility, any anomalies observed — are logged as part of the flight record. This documentation is retained and is available to the client on request.

All raw data captured during a flight operation is backed up to two independent storage locations before the drive leaves the site. A primary working copy and a secondary archive are maintained separately throughout the processing phase.

Data is stored and organized by client name, project name, and date — not by a generic internal file numbering system. If you request the underlying raw data for any engagement, we can retrieve it cleanly and quickly. Data is retained for a defined period post-delivery and can be made available on request.

Raw imagery and sensor data are processed using industry-standard photogrammetry and mapping software. For inspection deliverables, this means annotated image sets with location-tagged findings. For mapping deliverables, this means georeferenced orthomosaics, point clouds, or digital elevation models as appropriate. For agriculture deliverables, this means processed NDVI or multispectral indices overlaid on a georeferenced field map.

Before any deliverable is released, it is reviewed by the second founder — not the pilot who flew the mission. The reviewer checks: spatial accuracy, completeness of coverage, annotation quality, file format integrity, and whether the deliverable answers the question the client originally asked in scoping. If the QC review identifies a gap, the deliverable is corrected before release. It does not ship with a known deficiency and a note saying we will fix it later.

A structured written report covering findings, methodology, and coverage summary; annotated image files with georeferenced location tags; georeferenced orthomosaics in GeoTIFF format; point clouds in LAS/LAZ format; digital elevation or surface models; NDVI or multispectral index rasters for agricultural engagements; video footage in broadcast-standard MP4 where included in scope.

We do not deliver a folder of JPEG files and call it a report. Outputs are in formats that integrate directly into GIS platforms, CAD environments, or project management systems depending on your workflow. Format requirements are confirmed during scoping.

Deliverables are packaged and delivered via a secure link within the timeline confirmed at project scoping. A brief written summary accompanies every package explaining what is included, how to use it, and who to contact if anything requires clarification.