Drone insurance certificates: the COI clients ask for

A drone insurance certificate is the one page document an insurer or broker issues to prove that cover exists, and it is the single most requested piece of paper in commercial drone work. No federal rule requires it. The FAA asks for a pilot certificate and an aircraft registration and has nothing to say about insurance at all. The demand comes entirely from the other direction, from clients, site owners, general contractors, venues, and public agencies, none of whom will let an aircraft leave the case without one.

That distinction shapes how the document should be handled. A certificate is not a regulatory filing to be produced once and forgotten. It is a contract deliverable that gets requested per client, often per site, sometimes per job, with different named parties and different endorsements each time. This article covers what a certificate shows, what it deliberately does not do, where the requirement originates on federal and enterprise work, and how a program keeps a growing stack of them current without an administrator chasing a broker every Monday.

What the certificate shows and what it cannot do

A certificate summarizes policies in force: the named insured, the carriers, the policy numbers, the kinds of cover, the limits per occurrence and in aggregate, the effective and expiration dates, and the certificate holder it was issued to. It is standardized across the industry, which is why every one you receive looks broadly the same and why a client's procurement team can read yours in ten seconds. That familiarity is the whole value of the format.

What it cannot do surprises operators the first time it matters. A certificate is issued for information only and does not amend, extend, or alter the underlying policy. Writing a client's name in the description box does not make them an additional insured. Requesting a waiver of subrogation on the certificate does not create one. Both of those are endorsements to the policy itself, and if the policy does not carry them, the certificate saying so changes nothing. A client who asks for additional insured status is asking you to buy something, not to type something.

Where the requirement comes from

On federal work the requirement is written into the contract rather than left to negotiation. FAR 52.228-5 obliges the contractor to provide and maintain, at its own expense and for the entire performance of the contract, at least the kinds and minimum amounts of insurance set out in the schedule, and to notify the contracting officer in writing before commencing work that the required insurance has been obtained. The clause also requires the policies to carry an endorsement so that cancellation or any material change adversely affecting the Government's interest does not take effect until thirty days after written notice, or for whatever longer period state law prescribes.

Two details in that clause show up constantly in private sector contracts too, because it is where much of the market copied its language from. The first is the notice on cancellation, which exists so the buyer learns that cover has lapsed before the work does. The second is flow down: the clause requires its substance to be inserted into subcontracts for work on the installation. That is the mechanism by which a subcontracted drone operator inherits insurance obligations negotiated by someone several tiers above them, usually arriving as a certificate request with a deadline attached.

Handling requests without a bottleneck

Certificates arrive as requests, and requests arrive at whoever answered last time. In small programs that is the owner. In larger ones it becomes an operations coordinator with a broker's email address and a growing folder of PDFs, none of which are attached to anything. The predictable failure is the Friday mobilization that stalls because the site needs a certificate naming a party nobody has heard of and the person who handles it is on a plane.

The structural fix is to treat certificates as job documents rather than company documents. The certificate issued for one client covers that relationship, carries their endorsements, and belongs with their work, which is the same reasoning behind sizing each pilot's access to the jobs they are assigned. A pilot mobilizing to a site needs the certificate covering that site, not the company's entire insurance history across every client it has ever worked for. Scoping the document to the job also stops one client's certificate reaching another client's inbox, which is a small mistake with an outsized reputational cost.

Keeping a stack of certificates current

Certificates expire, and they expire on the policy's schedule rather than the client's. A twelve month policy generates a renewal date that invalidates every certificate issued against it, all at once, for every client holding one. Programs that discover this the slow way spend a week each year fielding polite emails from procurement teams whose vendor compliance systems have flagged them, usually while trying to mobilize on something urgent.

Getting ahead of it takes a list and a date. Every certificate issued goes on the record with the client it was issued to, the job or site it covers, the endorsements it reflects, and the expiration it inherits from the policy. When renewal comes, the reissue list already exists and the broker gets one instruction rather than fifteen. The same record answers the other question that arrives without warning, which is whether a particular client was ever named on a particular policy at the time a particular flight took place.

Common mistakes in drone insurance certificates

Treating the description box as an endorsement. Text on a certificate does not add an additional insured or waive subrogation. Only a change to the policy does that, and it usually costs money.

Sending a stale certificate. A certificate showing cover that expired last quarter proves former insurance. Vendor compliance systems catch it instantly, and mobilization stops while a new one is chased.

Letting one certificate serve every client. Endorsements and named parties differ per relationship. A generic certificate satisfies the file and fails the contract it was meant to satisfy.

Ignoring the flow down clause. Subcontracted drone work inherits insurance terms agreed several tiers up. Read the requirement before pricing the job, not after winning it.

Storing certificates in an inbox. Documents held in one person's email vanish when that person is unavailable, which is reliably the day a site asks for one at short notice.

FAQ

Does the FAA require drone operators to carry insurance?

No. Part 107 imposes no insurance requirement, so cover is entirely a commercial matter. Clients, site owners, and public agencies demand it through contracts, which makes it required in practice for almost all paid work.

How quickly can a broker issue a certificate?

Usually within a business day for a standard request against an existing policy. Requests involving new endorsements, such as additional insured status or a waiver of subrogation, take longer because the policy itself has to change.

What limits do clients typically ask a drone operator to carry?

It varies widely by sector and site, and the figure is set by the contract rather than by regulation. Enterprise and public sector work generally sets higher limits than small commercial jobs.

Who should be listed as the certificate holder?

The party that asked for it, named exactly as their contract specifies. A mismatch between the certificate holder and the contracting entity is one of the most common reasons a certificate gets rejected.

Closing thought

The certificate is a small document doing contractual work far out of proportion to its size, and almost every problem with it comes from treating it as proof rather than as a summary of something else. Cover lives in the policy. Endorsements live in the policy. The certificate only reports what is there, to a named party, on a date, which is exactly why it needs to be issued deliberately and tracked to an expiry.

If you are the person clients email when they want proof of cover before mobilization, FlybyOps was built for the operational record problem at the center of regulated drone work. A document vault with expiration tracking, a project and job hierarchy that scopes documents to the work they cover, role based access controlling who can reach a client's file, and an append-only audit log are all part of how the platform keeps the certificate a client was sent filed beside the job it cleared.