This page covers commercial drone (UAS) insurance records: liability and hull policy renewals, the aircraft each policy covers, and the client certificates and additional-insured endorsements tied to jobs. Pilot currency and drone registration are covered on Part 107 currency and drone registration tracking, and certificate collection in general on certificate of insurance (COI) tracking. (General information only - not legal, insurance, or coverage advice. See Sources.)
Remindax tracks policy terms, renewal dates, covered aircraft, limits you enter, certificate requests, owners, status, and documents you upload. It does not sell, quote, or compare insurance, read policy wording, or decide what a policy covers. Your broker, carrier, and policy documents answer coverage questions.
1. What is drone insurance tracking?
It is a dated record of every policy that touches your drone operation: type, carrier, policy number, the aircraft and serials listed, the limits on the declarations page, the term, the renewal date, and the owner. Around those rows sit the certificates and endorsements clients ask for before each job.
The FAA's small drone rule, 14 CFR Part 107, sets pilot, aircraft, and operating rules; the regulation text we checked does not contain an insurance requirement. Insurance expectations usually arrive through client contracts, site owners, or venues. Check what applies with your broker and your contracts. Remindax keeps the dates and sends reminders.
1.1 What sits on each row
Type, carrier, and policy number
Liability, hull, or combined, with carrier and policy number.
Covered aircraft and serials
Each listed drone with make, model, and serial.
Term and renewal date
Effective and expiration dates, plus your internal start date.
Declarations and certificates
Declarations page, endorsements, and client certificates.
2. What does a drone policy and aircraft register look like?
One row per policy, with the covered aircraft listed on it, the limits as written on the declarations page, the renewal date, an owner, and a status. The example is illustrative - carriers, numbers, limits, and dates are made up.
| Policy type | Carrier | Policy no. | Aircraft covered | Limits (per dec page) | Renewal date | Owner | Status |
|---|---|---|---|---|---|---|---|
| Drone liability | Carrier A | UAS-0001 | All scheduled aircraft | As stated | Jan 31, 2027 | Operations manager | Current |
| Hull / physical damage | Carrier A | UAS-0002 | Quad 1 (SN 1234), Quad 2 (SN 5678) | Scheduled values | Jan 31, 2027 | Operations manager | Current |
| Hull / physical damage | Carrier A | UAS-0002 | Mapping drone (SN 9012) | Not yet listed | - | Fleet lead | Add request sent |
| Drone liability | Carrier B | UAS-0300 | Branch 2 aircraft | As stated | Nov 15, 2026 | Branch manager | Renewal quote pending |
| Umbrella (if any) | Carrier C | UMB-0042 | Check wording | As stated | Jun 30, 2027 | Finance | Current |
Illustrative register only. Carriers, policy numbers, serials, limits, and dates are fictional. Record limits exactly as your declarations page states them, and check your policy wording for what each policy covers.
The Branch 2 policy renews in five weeks with no quote back, and the new mapping drone is flying while its add request is still open. Keep each aircraft's FAA registration date on a linked row on the Part 107 and drone registration page rather than another column here.
3. How do drone liability and hull policy renewals differ?
For tracking, they are two records that may or may not share a date. Liability is typically written for the operation; hull or physical damage is typically written for listed aircraft with a value for each. Some carriers combine them and some write them separately, so the register should not assume either way.
For reminders, each policy has an expiration date, the renewal takes time to quote and bind, and certificates already issued point at the old term. What each policy covers is in the policy wording, not on this page.
3.1 An example renewal timeline
| Step to track | Example offset | Example (expires Jan 31, 2027) | Reminder goes to |
|---|---|---|---|
| Send updated aircraft list and hours to broker | 90 days before | Nov 2, 2026 | Fleet lead |
| Renewal quote received and reviewed | 45 days before | Dec 17, 2026 | Operations manager |
| Renewal bound, new declarations uploaded | 14 days before | Jan 17, 2027 | Operations manager |
| Updated certificates sent to active clients | By expiration | Jan 31, 2027 | Client contact owner |
Illustrative only. These offsets are examples your team sets, not carrier or regulatory deadlines. Use your broker's actual timeline.
4. Why do covered aircraft changes need their own rows?
The aircraft list moves faster than the policy term. A new drone arrives, an older one is retired, a payload is swapped. If the policy schedules aircraft by serial number, each event can mean a change request to the broker - and a gap if nobody sends it.
New aircraft added
Log the purchase date, serial, and the date the add request went to the broker. Close the task when the updated schedule arrives.
Aircraft retired or sold
Archive the row with the date and ask the broker whether the schedule should change.
Incident or damage
Log the date. Insurer notice terms are in your policy; the FAA report under 14 CFR 107.9 is a separate clock.
Under 107.9, the remote pilot in command reports to the FAA within 10 calendar days any operation involving serious injury or loss of consciousness, or damage to property other than the drone unless repair cost, or value if a total loss, is $500 or less. Track it as its own dated task; the reporting stays with your pilot.
5. How should you track client certificates and additional-insured endorsements?
Clients such as construction firms, utilities, and event venues often ask for a certificate of insurance before a drone crew arrives, and some ask to be named as additional insured. Every request has a due date: the job start.
| Client / job | Job start | Requested | Policy | Certificate valid to | Owner | Status |
|---|---|---|---|---|---|---|
| Client 1 - roof survey | Oct 20, 2026 | Certificate | UAS-0001 | Jan 31, 2027 | Account lead | Sent |
| Client 2 - site progress | Nov 3, 2026 | Certificate + additional insured | UAS-0001 | Jan 31, 2027 | Account lead | Endorsement with broker |
| Client 3 - event filming | Dec 5, 2026 | Certificate | UAS-0300 | Nov 15, 2026 | Branch manager | Policy renews before job |
| Client 4 - annual inspections | Ongoing | Certificate on each renewal | UAS-0001 | Jan 31, 2027 | Account lead | Resend at renewal |
Illustrative only. Clients, jobs, and dates are fictional. What a client may require, and what wording an endorsement uses, is set by the contract and the carrier.
Client 3 is the one to catch: the job starts after the policy behind the certificate expires, so a fresh certificate is needed once the renewal is bound. If you also collect certificates from subcontracted pilots, the COI tracking page covers that side, and COI tracking software handles it at scale.
6. Which owner model works for drone insurance records?
Split the work by record type:
Operations manager
Owns each policy row, the renewal timeline, and the broker relationship.
Fleet lead
Keeps serials and the covered-aircraft list current and logs every add or removal request.
Account lead
Logs each certificate request against the job start date and uploads what was sent.
6.1 An example escalation ladder
- ✓Renewal 90 days out: the fleet lead is reminded to send the updated aircraft list to the broker.
- ✓No quote at 45 days: the operations manager is reminded by Email, SMS, or WhatsApp, with finance copied.
- ✓Certificate request open 5 days before a job: the account lead and operations manager are both reminded.
- ✓Expiration passed with no new declarations: the row turns overdue and escalates daily.
The offsets above are examples your team sets. If you track renewals across many business lines, insurance renewal reminder software shows how the same pattern works for every policy you hold.
7. How Remindax tracks drone insurance policies
Remindax is date-and-status tracking - not an insurer, a broker, or a flight operations platform:
Every policy on one register
Type, carrier, term, and declarations page, grouped by branch.
Aircraft linked to policies
Each serial sits under its policy, with open changes flagged.
Certificates tied to jobs
Each client request carries the job start date and the policy it relies on.
Exports by status
Renewals due next quarter, aircraft not yet listed, or certificates still open.
Remindax does not sell or quote insurance, issue certificates, request endorsements, or interpret policy wording. It holds policies, dates, aircraft lists, and owners on AWS hosting with encryption. GDPR-ready.
8. Why spreadsheets fail for drone insurance tracking
A spreadsheet holds serial numbers. It cannot warn that a job starts after its certificate's policy expires.
- xDeclarations pages stay in an email thread
- xNo alert when a renewal quote is late
- xNew aircraft fly before anyone asks to list them
- xCertificate requests live in inboxes
- xClients keep old certificates after renewal
- ✓Declarations uploaded to each policy row
- ✓Reminders at each renewal step you set
- ✓Open aircraft change requests flagged
- ✓Certificate requests dated to job start
- ✓Resend list of clients at each renewal
9. Key takeaways
- ✓Track one row per drone policy - liability, hull, or combined - with carrier, policy number, term, and declarations page on file.
- ✓Link each aircraft and serial to the policy that lists it, and log every add or removal request with a date.
- ✓Date every client certificate and additional-insured request to the job start, and resend certificates after each renewal.
- ✓Insurance expectations usually come from contracts and clients; check what applies with your broker and your policy wording.
- ✓Remindax tracks dates and status and reminds by Email, SMS, and WhatsApp. It does not sell insurance, issue certificates, or give coverage or legal advice. Free to start.
10. Frequently Asked Questions
Policy type, carrier, policy number, covered aircraft and serials, limits as stated on the declarations page, term dates, owner, status, and uploaded documents.
The FAA's small drone rule, 14 CFR Part 107, sets pilot, aircraft, and operating rules, and the regulation text we checked does not contain an insurance requirement. Insurance expectations usually come from clients, contracts, venues, or other rules that may apply to a job. Check with your broker and your contracts. This is not legal advice.
Track each policy on its own row, even when the carrier and renewal date match. If one policy combines both, use one row and note it. What each policy covers is in the policy wording, so ask your broker.
Add the aircraft and serial, log the date you asked your broker whether the schedule needs to change, and keep the task open until the updated schedule is uploaded.
Link each certificate to its policy. At renewal, filter for active clients whose certificate points at the old term and send fresh ones.
This page covers drone insurance policies, covered aircraft, and client certificates. Pilot currency and FAA drone registration dates are covered on Part 107 currency and drone registration tracking.
No. Remindax tracks dates, status, owners, aircraft lists, and documents you upload. Quotes, binding, certificates, and endorsements stay with your broker and carrier. Data sits on AWS hosting with encryption, and Remindax is GDPR-ready.
Yes - a forever-free plan, no credit card required.
Sources & References
Public educational material on drone operations and records - not legal, insurance, coverage, or regulatory advice. FAA rules checked October 9, 2026. Confirm current requirements with the FAA, your contracts, your broker, and your carrier. Premiums and limits are not restated here. This page does not provide filing or reporting instructions.
Never fly a job on a lapsed policy
Track every drone policy, covered aircraft, and client certificate - automatically.
GDPR-ready | AWS secure cloud | Encrypted storage | Setup under 5 minutes