What general contractors miss when they bring reality capture in-house
There’s a decision happening in construction right now that almost nobody is running past their legal department.
General contractors are bringing drone work in-house. The logic is easy to follow. Drones have gotten cheap and easy to fly. The software is largely automated. Somebody on the project team already owns a Mavic and flies it on weekends. Why keep paying a vendor for something that looks like a fifteen-minute task?
I’ve been in this business for thirteen years, and I want to say up front that this can be done well. Some contractors run genuinely mature UAS programs — a dedicated program manager, a written operations manual, scheduled aviation coverage, documented pilot currency and recurrency standards, and real enterprise data governance. That’s a department, and it’s a legitimate strategic choice. If that’s what you’re building, build it, and I’ll help you.
But that’s usually not what gets built. What usually gets built is a job duty added to a project engineer’s already-full plate, approved at the project level, with nobody in risk management or legal in the room.
And that’s where the exposure lives.
The exclusion nobody reads
Start with insurance, because it’s the item most people assume is handled and most often isn’t.
Standard commercial general liability forms carry an aircraft exclusion. It’s been in there for decades, written for a world where “aircraft” meant something with a pilot inside it. ISO also publishes drone-specific exclusion endorsements, CG 21 09 and CG 21 10, which insurers have been attaching to construction policies for years now.
In Philadelphia Indemnity Insurance Co. v. Hollycal Production, Inc. (C.D. Cal. 2018), a drone operator was shooting a wedding when the aircraft struck a guest and permanently blinded her in one eye. The insurer went to federal court seeking a declaration that it owed nothing. The court agreed. It held that a drone is an “aircraft” within the meaning of the policy’s exclusion, that the carrier had no duty to defend or indemnify, and that the insurer was entitled to recover the defense costs it had already advanced.
Read that last part again. Not only was there no coverage — the insured had to pay back the money the carrier had already spent defending the claim.
Coverage for drone operations generally has to be granted back deliberately, either by scheduling the aircraft on an endorsement or by writing a standalone aviation policy. It does not happen by default, and it does not happen because you assumed your CGL was broad.
There’s a second wrinkle worth knowing. CG 21 09 contains no insured-contract exception. So if you’ve signed a contract agreeing to indemnify an owner for incidents on their site, and a drone incident is what triggers that indemnity, the liability you assumed by contract may also sit outside your coverage.
Six more questions worth asking
Insurance is the sharpest issue but it isn’t the only one.
Who is the defendant? When your own employee is the remote pilot in command, the claim lands on you directly under respondeat superior. There is no one upstream to tender to and nobody standing between the claimant and your balance sheet. When a qualified vendor flies, you get contractual indemnity, additional-insured status, a waiver of subrogation, a certificate of insurance in the file, and a separately insured defendant. Insourcing doesn’t reduce that risk. It retains all of it.
What happens to your safety numbers? An injured drone operator is a workers’ compensation claim and, in most cases, an OSHA recordable. Rotor lacerations, eye injuries, lithium-polymer battery fires, and falls from a roof edge while acting as visual observer are all entirely foreseeable. Your TRIR and EMR are bid currency on the work you want most. Contractor personnel don’t touch either number.
Is Part 107 enough? A Part 107 remote pilot certificate is a written knowledge test. There is no flight-hour minimum, no practical exam, and recurrent training runs on a 24-month cycle. It establishes legal authority to operate. It is not evidence of proficiency, and it is not a risk program. A real program defines initial qualification, recurrency intervals, proficiency checks, aircraft maintenance and battery-cycle logging, and disqualification criteria — and names who is accountable for enforcing them. Without that, plaintiff’s counsel will put your org chart on the screen in deposition and walk the jury through who trained the pilot, on what, and when.
Who holds the airspace authorization? A lot of retail, industrial, and distribution sites sit in controlled airspace. Somebody has to obtain and document LAANC authorizations, track their expirations, and establish the waiver basis for any night, beyond-visual-line-of-sight, or over-people operation. FAA enforcement can reach both the certificated airman and the employer, and a pattern of undocumented operations is discoverable. The compliance bar is also rising rather than falling — the FAA’s proposed Part 108 framework pushes responsibility further toward documented organizational programs with trained personnel and written risk controls, rather than resting on individual pilot judgment.
Who controls the imagery after a claim? This is the one I’d most want a construction attorney to think about. Every flight creates a timestamped record of site conditions. Managed well, that is the single best defense asset you can have in a defect or delay dispute — it’s the difference between arguing about what the site looked like and showing it. Managed casually, it becomes the opposite: an inconsistent capture cadence that opposing counsel characterizes as selective, imagery establishing that you knew or should have known about a condition, and no chain of custody for any of it. And if a field employee wipes a memory card after an incident, that’s potentially spoliation. So the practical question is simple. Does your project imagery live in an enterprise system with a retention schedule, or on a project engineer’s personal cloud account?
Who owns privacy and continuity? Adjacent-property overflight, incidental capture of neighbors and passersby, and video of your own workforce implicate state UAS surveillance statutes, trespass and nuisance theories, and whatever confidentiality obligations you owe the owner. Who reviews footage before it’s distributed, and to whom? Separately, internal drone programs almost always rest on one or two enthusiasts. When they take another job, the flying stops mid-project and the historical record is orphaned in a departed employee’s account — across however many concurrent jobs and states you’re running.
The analogy that clarifies it
Here’s the thing that finally made this click for me.
You self-perform earthwork. You don’t put an intern on the dozer. You use credentialed operators with documented training, equipment-specific coverage, and a superintendent who owns the risk. You don’t hand the crane controls to a project engineer during a wall tilt because it trims a line item.
A drone is the only thing on your jobsite regulated by a federal aviation authority. Somehow it’s the one piece of equipment we’re comfortable assigning to whoever on the team is into gadgets.
The dividing line was never in-house versus outsourced. It’s credentialed versus collateral duty.
If what you’re building is a real department — a program manager, an ops manual, scheduled aviation coverage, documented currency, enterprise data governance — then build it. I mean that. Our industry is better off with more contractors who take this seriously, and we’ll help anyone who wants to get there.
But if what’s actually being created is a duty added to somebody’s existing job description, then the savings on the capture line are being financed by an uninsured aviation exposure sitting on your balance sheet. And the person who tends to discover that is your carrier’s coverage counsel, after the claim.
Four words
There’s one question that resolves most of this, and it takes about a day to answer.
Walk it down to your risk manager and ask for it in writing:
“Show me the endorsement.”
If the answer takes more than a day to produce, you already have your answer.
We’ve put these seven questions into a one-page risk brief you can forward to your legal counsel and your insurance broker. Request the brief — no pitch attached.
This article is a business risk summary, not legal advice. Every item above should be verified with your own legal counsel and insurance broker against your specific policy forms, jurisdictions, and project requirements.
