Sooner or later somebody in an operation that buys drone surveys asks the obvious question: the aircraft costs less than a few of these jobs, so why are we not doing this ourselves?
It is a fair question and the answer is not always "hire us". Some operations should absolutely run their own program. The mistake is comparing the price of an aircraft to the price of a survey, because the aircraft is the small part.
The real cost stack of an in-house program
Buying the drone is the beginning. A program that produces data anyone will rely on also carries:
- Certification and currency. Pilots need the appropriate Transport Canada certification for the operations they intend to run, and it has to stay current. That is time and money on a repeating cycle, not once.
- Aircraft and payload refresh. Hardware ages, batteries have a finite life, and the payload usually matters more than the airframe. A thermal or multispectral sensor that produces defensible data is a different purchase from a camera drone.
- Insurance. Aviation liability at the limit your own contracts demand — which is often the limit you already require of your contractors.
- Software. Photogrammetry or point-cloud processing licences, and the compute to run them, on an ongoing basis.
- Procedures and documentation. Site-specific flight plans, hazard assessments, emergency procedures, maintenance records, flight logs and a data-retention practice. Producing these once is work; keeping them current is a role.
- Skill, which is the expensive part. Flying is the easy skill to acquire. Producing a volume that survives an audit, or a thermal report whose severity ranking means something, is a practised competency that decays without repetition.
- Somebody's time. Usually the least honestly counted item. The program lives in someone's job, and their normal job does not shrink to make room for it.
None of this makes an in-house program a bad idea. It makes the comparison a program-versus-service comparison rather than a hardware-versus-invoice one.
Utilisation decides it more than anything else
The single most predictive question is how often you would actually fly.
The fixed costs above are almost entirely independent of how many flights you do. Spread across weekly flights they are small per flight. Spread across a handful of flights a year they are large — and the low-frequency case has a second problem: the crew never becomes practised, so the flights you do fly are the ones least likely to produce usable data.
The honest test is not "would we use it" but "what is on the flight calendar", written down, for the next twelve months. Programs justified on the flights people imagine doing tend to underperform the business case. Programs justified on a recurring, already-scheduled cadence tend to beat it.
Where in-house genuinely wins
- High, regular frequency. Weekly construction progress capture, monthly stockpile cycles, routine site documentation. Repetition is what makes the fixed cost small and the crew good.
- Response time measured in minutes. If the value is being airborne within the hour — an incident, a spill, a storm, a search of your own ground — nobody can mobilise faster than someone already on site.
- Access-restricted sites. Where escorting an outside contractor is genuinely harder than certifying your own staff, or where the imagery cannot leave your control at all.
- Work that is simple and repeatable. A well-defined, unchanging capture over the same ground is exactly the kind of task an internal program executes well.
Where contracting wins
- Occasional or seasonal work. A few flights a year never repays the fixed cost or builds the skill.
- Specialised payloads. Radiometric thermal, methane detection, LiDAR and collision-tolerant confined-space aircraft are expensive to own and expensive to become good with. Renting the capability with the operator attached is usually the cheaper competency.
- Work that has to survive challenge. When a volume feeds a financial statement or an inspection finding feeds an integrity decision, an independent operator with their own quality assurance and insurance is a different evidentiary position from an internal file.
- Peaks. Turnarounds, outages, incident response and month-end all want capacity you do not need the rest of the year.
- The compliance overhead itself. Certification currency, registration, authorisations, insurance and records are a contractor's problem to carry. In-house, they become yours — and they are the part that is quietly dropped first.
How in-house programs actually fail
They rarely fail loudly. The pattern is consistent:
- The certified pilot leaves, changes role, or gets busy, and the program is one person deep.
- Recurrent training lapses quietly and nobody notices until an audit or an incident.
- The aircraft is fine but the processing licence was never renewed, so captured data sits unprocessed.
- Nobody owns the data. Files live on the pilot's laptop and cannot be found two years later when the dispute arrives.
- The work drifts from "map the site" to "get some photos", because the discipline that made the output measurable was never written down.
Every one of these is preventable, and preventing them is what distinguishes a program from a drone.
The split most operations end up with
In practice the durable arrangement is usually not either/or:
- In-house for high-frequency, low-complexity, fast-response capture — progress photography, routine site documentation, a quick look after an event.
- Contracted for the specialised payloads, the audit-grade measurements, the peaks, and anything whose result has to stand up to somebody else's scrutiny.
That split puts the fixed cost where the utilisation is, and puts the specialised competency where the consequences are.
Before you decide
- Write down the flight calendar for the next twelve months. Actual scheduled work, not aspiration.
- Price the whole stack — certification and currency, aircraft and payload refresh, insurance, software, and the staff time to run it — not just the aircraft.
- Name who owns the program when the person who champions it is unavailable for a month.
- Decide which outputs must survive external challenge, and be honest about whether an internal file is the right place for those.
- Run the numbers per flight at your realistic frequency, then compare that to a quote. If it is close, contract it — the difference is not worth the operational overhead.
We will tell you honestly which side of that line you are on. Some of the operations we work with fly their own aircraft weekly and call us for the thermal, the LiDAR and the confined-space work, which is exactly the right answer for them.