Insurance is a launch dependency, not a substitute for an operating authorization. A retailer evaluating aerial delivery may sign a contract with a certified operator, install equipment on store property, transfer goods into an aircraft, and receive a customer complaint after an unsuccessful drop. Each step creates a different exposure. This 2026 checklist helps retail, logistics, municipal-site and integrated-UAV-system buyers ask who bears each risk, what coverage actually responds, and how a claim moves between parties.
The analysis is focused on U.S. commercial package delivery. It is not an insurance quotation, universal coverage mandate, legal opinion, or statement that any named operator carries a particular policy. Coverage varies by policy wording, endorsements, exclusions, operation, contract and jurisdiction. Use it to prepare questions for qualified aviation-insurance brokers and counsel before signing a service agreement.
1. Draw the operating and custody boundaries first
Before comparing insurance certificates, map the full order journey: eligibility decision, store picking and packing, secure staging, release to the UAS operator, launch, flight, delivery method, handoff confirmation, exception handling and any return. Ask whether the aircraft is owned by the operator, leased from an integrator, or supplied by the merchant. An aircraft manufacturer, air carrier, network orchestrator and property host can be four different legal entities.
Record the exact point when care, custody and control of the goods changes hands. For a drop-off network, differentiate an aircraft landing, a tethered lowering system and a release into a designated area. Those methods affect where property or injury exposure may occur. See our retailer integration checklist for checkout and delivery handoff requirements.
2. Ask about seven distinct coverage or contract exposures
Exposure Primary due-diligence question Evidence to request Third-party aviation liability Who responds to bodily injury or property damage caused by flight operations or ground handling? Policy declarations, aviation liability wording, applicable limits and exclusions. Aircraft hull and onboard equipment Who pays if a drone, avionics, dock equipment, batteries or detachable payload are damaged? Insured schedule, values, deductible, parts/spares and non-owned equipment terms. Cargo and goods in transit Are customer goods covered while in staging, onboard, descending, awaiting collection and during a failed delivery? Cargo or goods-in-transit coverage; valuation, exclusions, per-item and aggregate limits. Store and hub premises Who bears a loss arising from a launch pad, power supply, roof installation, ground staff or visitor at the site? Site owner and operator policies, occupancy permissions, premises allocations and contracts. Data, command links and cyber Which party handles compromised routing data, customer addresses, payment-system interfaces, or control-service interruption? Cyber wording, incident obligations, subcontractor scope and network/service contracts. Non-owned or hired equipment Does the contract cover leased drones or assets owned by another member of the delivery network? Hired/non-owned endorsements, owner schedules and additional insured wording where appropriate. Service interruption and replacement Who pays refunds, substitute courier costs or suspended-service charges? Service-level credits, alternate-hire provisions, business-interruption terms if applicable, and carve-outs.
These are risk categories, not a claim that one policy covers them all. Tokio Marine Highland’s published commercial drone product information, for example, distinguishes hull and third-party liability from endorsements such as cargo, non-owned liability, alternative hire and digital-asset extensions. Its advertised options are evidence that buyers should inspect wording—not evidence that any other policy includes those protections. SkyWatch’s January 2026 policy overview similarly separates time-limited liability policies from optional aircraft physical-damage coverage.
3. Verify the FAA operating pathway separately
Under current FAA guidance, Part 107 can allow certain compensated intrastate package transport if all applicable limits are met, including visual line of sight and a total aircraft-plus-payload weight below 55 pounds. For carriage of another party’s property for compensation beyond visual line of sight, the FAA identifies Part 135 air-carrier certification and applicable exemptions or waivers as the current pathway. Confirm the actual certificate holder, operations specifications, aircraft, geography, delivery method and any relevant authorizations; a platform logo or a generic pilot certificate is not enough.
Regulatory authority and insurance are separate diligence tracks. U.S. law also contains air-carrier insurance and financial-responsibility provisions, including 49 U.S.C. § 41112. Do not infer from that provision a universal drone-policy limit or its application to a specific transaction. Ask aviation counsel or an appropriately qualified broker what filing, minimum and indemnity requirements apply to the particular carrier, operation and contract. FAA approval is not proof of insured status, and a certificate of insurance is not proof of flight approval.
Product exclusions matter, too. The FAA states that Part 107 prohibits transporting dangerous goods and describes additional authorization requirements for Part 135 UAS hazardous-material programs. A merchant should classify products before allowing them into the drone-eligible catalog rather than relying on a carrier to discover a prohibited item at launch.
4. Use a responsibility matrix rather than a blanket indemnity clause
Event Operational owner to identify Contract and claim question Customer order accepted Retailer or marketplace Who verifies eligible addresses and products; who issues refunds? Item packed and staged Store or fulfillment partner What seals, weight checks and scan records establish handoff condition? Aircraft loading and launch Authorized operator and site host Who controls access, weather go/no-go decisions, personnel and launch infrastructure? In-flight transport FAA-authorized operating entity Who receives telemetry and flight-event records; whose aviation policy responds? Lowering, landing or release Operator; possibly a delivery-endpoint vendor Where exactly does physical custody terminate, and what proves completion? Failed, damaged or misdelivered order Merchant, carrier and customer support Who contacts the customer, funds replacement delivery and preserves evidence? After-flight equipment or data loss Asset owner and affected service provider Who repairs the aircraft, secures customer data and assesses subcontractor responsibility?
This is a prompt for contract negotiation, not a predetermined assignment of legal fault. Each contract should identify responsible entities and address mixed-cause events, third-party claims and disputes without assuming that responsibility always falls on the party physically closest to the aircraft.
5. Twelve questions to ask before accepting a certificate of insurance
- Who is the named insured? Match its legal name to the carrier, asset owner and actual service provider.
- Which services are declared? Confirm delivery, BVLOS where applicable, payload lowering, rooftop launch, urban or residential routes, and any other relevant flight profile.
- When does coverage apply? Examine policy dates, territories, operating hours, scheduled aircraft and any pilot or platform restrictions.
- What are the limits? Distinguish each occurrence, aggregate, cargo sublimit, aircraft insured value, deductible and self-insured retention.
- Are there aviation exclusions? Do not assume a general business liability policy responds to aircraft operations.
- Is the merchant or landlord an additional insured where appropriate? Require the actual endorsement and verify the covered activity rather than relying only on a certificate remark.
- What about contracted parties? Check subcontractors, marketplace orchestration, manufacturers, temporary staff and non-owned or hired aircraft.
- Does cargo protection survive each handoff? Specify staged goods, loading, aerial transport, release and post-delivery custody.
- What exclusions might defeat a claim? Ask about unauthorized flights, prohibited cargo, weather, maintenance, cyber events and misdelivery.
- Who receives cancellation or material-change notice? Define the contract obligation and proof method; do not assume a certificate automatically creates that right.
- How do claims and deductibles work? Identify who reports, cooperates, pays retention and can settle a claim.
- Who validates the documents? A named risk owner should review policies with counsel/broker before launch and at renewal, not merely file a PDF.
A certificate of insurance is primarily a summary. Requested policy language and endorsements—not aspirational contract language—determine whether an insurer is obligated to respond. Do not publish or claim any particular coverage amount as a generally required federal minimum unless a current rule and transaction-specific facts support it.
6. Put these terms in the services agreement
- Operating scope: authorized aircraft, locations, launch sites, routes, cargo categories, subcontractors and permitted service windows.
- Responsibility and indemnification: defined event ownership, defense and tender procedures, fault allocation and negotiated liability caps.
- Insurance schedule: required coverage lines and limits, exclusions, additional-insured requirements, deductibles, evidence, renewal and change notices.
- Data governance: who stores delivery imagery, location data, flight logs and customer information; retention, access and breach-notification duties.
- Incident handling: immediate safety response, named contacts, evidence preservation, escalation, claims intake and communications to customers or regulators.
- Commercial failure modes: non-deliverable addresses, wind or weather shutdowns, equipment downtime, consumer refunds, replacement couriers and service-credit formulas.
- Launch gates: no operational start until permits, aviation approvals, acceptable policy evidence, site permissions, testing and training are documented.
- Exit and continuity: site restoration, customer-data export, return of aircraft and equipment, open claims and post-termination cooperation.
7. Build a 24-hour incident plan before the first delivery
A practical plan identifies a field safety lead, aviation operator, merchant support lead, insurer/broker contact, property owner and communications approver. Define what personnel should do when a drone makes an unscheduled landing, a package falls outside the delivery zone, someone is injured, a customer disputes receipt, or an endpoint loses connectivity. Separate immediate life-safety action from later claims investigation and public communication.
For Part 107 operations, FAA guidance requires certain accidents to be reported within 10 days, including serious injury/loss of consciousness or qualifying damage to property other than the drone exceeding $500. See the FAA accident reporting FAQ. Do not apply that single Part 107 test to every Part 135 event: certificate conditions, other FAA or NTSB reporting obligations and contractual deadlines may differ. The operator should maintain a reporting matrix covering the actual authority under which it flies.
Preserve order timestamps, packaging scans, relevant video or telemetry under an established privacy policy, aircraft configuration, weather, customer support records and the certificate/endorsement set in force at the time. Prevent unnecessary retention of personal imagery. Name who can speak publicly and who can share incident records with insurers and regulators.
8. Model the coverage cost in cost per completed delivery
Insurance expenses are part of network unit economics even when an operator bundles them into its service price. An illustrative $24,000 annual insurance expense spread over 80,000 completed orders adds $0.30 per order; at only 20,000 completed orders it contributes $1.20. These are arithmetic examples, not insurance premium benchmarks or quotes. Deductibles, cargo losses, claim reserves, downtime and site coverage can add costs not captured by that simple allocation.
For procurement comparisons, ask the supplier whether insurance and expected claims losses are included in the quoted per-delivery rate, how the cost changes with route density, and which loss events flow through to the merchant as reimbursements or chargebacks. Request scenario assumptions rather than an unsupported industry-average premium. Pair this analysis with our complete UAV system RFQ template.
9. Copyable insurance diligence checklist
- Identify all legal entities: merchant, carrier, aircraft owner, ground-infrastructure owner, software platform and subcontractors.
- Map custody for each product type and delivery method, including unsuccessful delivery and returns.
- Confirm aviation operating authority separately from insurance and local site permissions.
- Request certificates, relevant policy schedules, applicable endorsements, exclusions and renewal dates.
- Confirm third-party liability, aircraft/hull, cargo, site, cyber and hired/non-owned exposures as applicable.
- Agree responsibility for customer injury/property claims, product loss, failed delivery, data incidents and regulatory reports.
- Assign deductibles, self-insured retentions, defense obligations and evidence-preservation duties.
- Test the incident notification tree and customer support workflows during a controlled pilot.
- Add periodic checks for material changes in route, payload, aircraft, subcontractor or operating authority.
- Have qualified counsel and an aviation broker review the final contract and policies before live service.
Buyer FAQ
Does FAA approval mean the drone-delivery company is insured for my retail site?
No. Flight authority and coverage evidence answer different questions. Request current documentation for the actual service and named entity, and verify any site-specific contractual requirements.
Does a merchant automatically need its own aviation policy?
Not automatically. The answer depends on who flies, owns the aircraft, operates the hub, assumes liabilities, and what the existing business policies exclude. A broker should examine the full contractual and operational arrangement.
Is customer merchandise insured by the aircraft hull policy?
Not necessarily. Hull coverage generally addresses damage to the aircraft, whereas customer merchandise may require cargo or another expressly applicable coverage arrangement. Verify declarations, valuation and custody terms.
How does this relate to vendor selection and commercial viability?
Treat risk diligence as a pass/fail procurement gate before using estimated delivery costs or customer demand to justify a program. A fast or inexpensive service that has unresolved liability, cargo or launch-permission gaps is not launch-ready. Compare operator assurances against documented evidence.
Sources, limits and independence
Primary guidance: FAA Part 135 UAS package delivery, FAA Part 107 package-transport FAQ, FAA hazardous-material guidance, FAA incident reporting, and 49 U.S.C. §41112. Published coverage examples: Tokio Marine Highland and SkyWatch. References were reviewed October 24, 2026. Coverage terms and regulatory rules should be rechecked before a transaction.
UAVPackage.com is an independent editorial resource. Mention of an operator or insurer is for education only and does not imply an endorsement, commercial relationship or buyer interest. For potential acquisition or strategic use of the developed site and domain, see the UAVPackage.com strategic inquiry page.
