BVLOS Drone Connectivity Buyer’s Guide (2026): SATCOM, Cellular and C2 Acceptance Tests

UAVPackage.com | Independent systems procurement guide | Prepared November 3, 2026

Executive takeaway. A drone’s communications package is not a single modem subscription. Buyers must distinguish safety-relevant command and control (C2), operational telemetry, detect-and-avoid or traffic services where applicable, and commercial payload data. The right purchasing question is not “Does this aircraft have satellite internet?” It is “Can this particular aircraft and operation maintain an acceptable control-and-monitoring service under an independently verified safety case, at a sustainable cost?”

On November 2, 2026, Viasat and Galaxy 1 Communications announced a production-services agreement for Viasat’s Velaris uncrewed-aircraft connectivity ecosystem. Galaxy 1 says its partner-enablement layer covers onboarding, provisioning, billing, terminal management, service restoration, third-party APIs and operational visibility. This is an important commercial integration milestone, but the announcement does not establish universal route coverage, FAA approval for any particular operation, a published network SLA, or an installed-fleet count. See Viasat’s announcement.

This guide is intended for drone delivery operators, logistics providers, aircraft OEMs, public-safety agencies, software integrators and procurement teams comparing a complete connectivity service—not merely a radio module. It is independent of Viasat, Galaxy 1 and the other vendors discussed.

1. Separate the traffic classes before choosing a network

Command and control (C2) includes the communications needed for the remote crew or automated ground system to command and monitor an aircraft. It can have safety-critical requirements. Flight telemetry includes aircraft position, system health, power and alarms; some telemetry is safety-relevant and some is operational. Payload data may include video, sensor files, delivery pictures, manifests or customer notifications. Service orchestration includes provisioning, route activation, billing, fleet identities, customer APIs and incident-management records.

Do not buy these classes under one unqualified promise of “connectivity.” Ask the operator and aircraft manufacturer which messages are safety-related for the intended concept of operations (ConOps), which can tolerate buffering, and which must have independent priority or segregation. RTCA’s SC-228 committee develops standards for UAS C2, detect-and-avoid and navigation; citing a standard is not equivalent to demonstrating that a specific aircraft, network and operation has obtained a regulator’s approval. RTCA SC-228.

A satellite service may be part of the safety architecture and still require separate analysis of aircraft automation, ground control, lost-link behavior, spectrum authorization and operational approvals. U.S. applicants should check the FAA authorization route appropriate to their operation rather than assume a supplier’s commercial launch grants BVLOS permission. FAA Section 927 waiver guidance and our BVLOS regulatory overview provide starting points, not legal advice.

2. Compare four bearer architectures, not four marketing slogans

Architecture	Where it can help	Principal procurement risk	Evidence to request
Dedicated terrestrial radio	Known routes and controlled infrastructure	Terrain, line-of-sight limitations, licensed-spectrum and site costs	Link budget, surveyed route, interference and failover records
Public or private LTE/5G	Coverage where mobile networks support the required airborne geometry	Airborne coverage differs from street-level maps; congestion and carrier constraints	Measured altitude/route coverage, carrier terms, roaming tests
L-band satellite connectivity	Remote corridors and network diversity	Terminal mass, antenna placement, throughput limits and service fees	Approved terminal integration, route-specific availability and latency distribution
Managed multi-bearer solution	Combining complementary links for resilience	Handover logic, common-mode faults and operational complexity	Transition logs, failover thresholds, duplicate-message behavior and recovery tests

These are evaluation categories, not claims that any individual bearer automatically meets aviation safety requirements. Assess end-to-end availability for the specific mission, not coverage-map color. A flight with a 20-minute coastal segment, a hospital campus transfer or an urban last-mile delivery can have very different link risks.

Viasat markets Velaris as an L-band connectivity service and has previously described work with uAvionix integrating satellite and terrestrial links. A 2024 announcement describes uAvionix’s use of multiple datalinks and a Link Executive Manager; those descriptions are supplier claims and should be subjected to the acceptance tests below. Viasat/uAvionix announcement.

3. Define the mission before requesting a quote

Provide each supplier with a written mission envelope: operating geography and route polygons; launch, recovery and dock locations; minimum and maximum planned flight altitudes; aircraft mass and endurance; payload weight; operating temperature and weather limits; number of concurrent aircraft; staffing model; dispatch-system interface; intended fail-safe landing locations; and the regulator’s current authorization status.

Specify the environmental assumptions used in each demonstration. A rooftop antenna tested on a clear day is not evidence for a low-altitude route past industrial structures during precipitation. Require the vendor to state where the evidence stops. For any marketed “global” product, confirm whether the countries, airspace, frequencies, terminals and subscriber agreements needed for your operation are actually supported.

Airborne integration: request terminal and antenna dimensions, weight, center-of-gravity implications, power draw by operating mode, heat dissipation, vibration compatibility, mounting restrictions, electromagnetic compatibility evidence, software compatibility, and any impact on usable payload or endurance. The lightest advertised terminal is not necessarily the terminal or installation approved for the intended aircraft.

Ground integration: identify who owns the control station, ground gateways, cloud accounts, encryption keys, API credentials, logging, dispatch integration, and troubleshooting. A communications reseller, aircraft OEM, mobile operator and flight operator may all be different contract parties. Assign a named party to each interface.

4. Contract measurable service objectives

Do not accept a network availability percentage by itself. A useful service-level schedule identifies the measurement point and counting rules. Ask for route-qualified, time-stamped tests of the following, with mutually agreed thresholds documented before testing:

End-to-end C2 message latency: median, 95th and 99th percentile; define the source and destination endpoints.
Packet delivery and age of information: dropped, duplicated, stale or delayed messages under representative load.
Availability: minutes when the required application-level service is usable, not merely when a radio registers to a network.
Bearer transition: detection time, handover duration, session continuity, order preservation and the aircraft’s autonomous response.
Coverage exceptions: terrain shadowing, terminal orientation, hub congestion, maintenance and planned outages.
Security: fleet identity lifecycle, key rotation, access controls, encryption boundary, vulnerability response and breach notification.
Observability: alerts, event IDs, uptime history, exportable logs, customer access, retention periods and root-cause reports.
Support: severity definitions, response and restoration commitments, credits, exclusions, spare terminal stock and replacement times.

Put the supplier’s actual numerical commitments into the contract; the values above are requested metrics, not claims about Viasat, LTE or any other service. For a regulated operation, the aircraft manufacturer’s safety requirements and regulator’s approvals may impose stricter constraints than a commercial SLA.

5. Eight acceptance tests to include in the RFP

Test 1 — Hardware and SWaP verification. Weigh the installed terminal, antenna, mounts and cabling; measure peak and steady power consumption; verify flight endurance and thermal behavior against the aircraft’s approved configuration. Deliverables: signed integration drawing and test log.

Test 2 — Route coverage and performance. Run representative outbound, return and contingency routes at the intended altitudes and traffic load. Report all outages, latency percentiles and unusable segments on a georeferenced timeline. Deliverable: raw and summarized data, not a screenshot of a coverage map.

Test 3 — Lost-link safe state. Simulate loss of every planned C2 bearer at defined flight phases in a controlled test environment. Observe the aircraft’s documented contingency behavior and recovery logic. Deliverable: crew signoff, traces and exception register; do not perform unsafe field testing without authorization.

Test 4 — Multi-bearer transition. Remove one bearer under load, then restore it. Verify no contradictory control commands, safe stale-command handling, and deterministic rejoin. Deliverable: synchronized aircraft, network and ground-station logs.

Test 5 — Security and identity lifecycle. Provision a new aircraft, rotate credentials, revoke a compromised account and decommission a terminal. Demonstrate that revoked identities cannot connect. Deliverable: access logs, architecture and audit evidence.

Test 6 — Dispatch and traceability. Trigger a delivery in the dispatch platform; correlate aircraft/network identifiers, flight state, delivery proof and incident tickets. Deliverable: versioned API schema, trace IDs, reconciliation records and sample error payloads. See our drone-dispatch software integration checklist.

Test 7 — Incident restoration. Simulate a terminal fault, provisioning problem or cloud outage. Measure time to detect, diagnose, restore and document the incident, including responsibility between OEM, service provider and integrator. Deliverable: operational runbook and complete timeline.

Test 8 — Billing reconciliation and scale. Activate a second aircraft fleet, change usage tiers, and reconcile line items for airtime, terminals, API access, managed services, deployment work and support. Deliverable: sample monthly invoice with explicit units and overage calculations.

Before production cutover, require all critical tests to pass and document any conditional approvals, remaining risks, owners and expiry dates. An excellent network performance graph cannot offset an untested lost-link behavior.

6. The financial model: price the mission, not the modem

Compare offers on a common mission basis. A practical annual cost expression is:

Annual connectivity program cost = recurring airtime + managed service + platform/API fees + support + replacement reserve + allocated ground infrastructure + annualized installation/integration costs.

Then divide by completed, eligible deliveries or scheduled aircraft-hours as appropriate, explicitly recording flights canceled for weather, airspace, maintenance, unavailable connectivity or merchant constraints. Do not compare an all-in managed service against a bare modem plan.

Illustrative model, not market pricing: Suppose 10 aircraft have $100/month each in connectivity charges, a shared platform costs $600/month, support costs $300/month, and annualized hardware/integration costs $9,000/year. The annual program total is (10 × $100 × 12) + ($600 × 12) + ($300 × 12) + $9,000 = $31,800. At 15,000 completed deliveries, the communications-program allocation is $2.12 per delivery. At 7,500 deliveries, it rises to $4.24 without any price change. The example intentionally excludes aircraft, labor, insurance and other logistics costs. See our drone-delivery unit-economics worksheet.

Ask suppliers to quote a base case and sensitivity to 50%, 100% and 150% of the planned number of flights. Contract exits, minimum commitments, roaming charges, terminal replacements, and log-export costs should be visible.

7. A defensible 100-point vendor scorecard

Evaluation group	Points	Minimum evidence
Safety case and lost-link demonstration	25	ConOps mapping, documented contingency tests, authorization dependencies
Route-level performance and resilience	20	Representative data, percentiles, outages, failover traces
Aircraft integration and SWaP	15	Installed measurements, thermal/EMC evidence, endurance impact
Cybersecurity and operational observability	15	Identity, audit, incident response and exportable logs
Interfaces and lifecycle management	10	Versioned APIs, provisioning, billing, terminal support
Full lifecycle commercial terms	10	Unit prices, sensitivity, SLAs and exit conditions
Referenceability and demonstrated support	5	Similar mission references and accessible escalation contacts
Total	100	Compare evidence, not promises

Establish deal-breakers in advance: authorization incompatibility, unverified lost-link safety response, an unacceptable security boundary, or failure to support essential dispatch data. A high composite score does not waive any such requirement.

8. What the November Viasat–Galaxy 1 announcement changes—and what it does not

The announced production-services arrangement is most relevant to organizations that need repeatable provisioning, managed terminals, APIs, invoicing and operational support across fleets, rather than a one-off radio trial. It indicates a shift toward service delivery infrastructure. It does not publish an aircraft-level safety certification, routes approved to operate BVLOS, a list of paying drone operators, or comparable SLA metrics. Procurement teams should request these items directly and avoid substituting commercial partnership language for validation. Primary announcement.

A nearby market signal is DoorDash Air’s September 30 announcement that its delivery system combines aircraft with ground infrastructure, merchant handoffs and order data. These integrations are why network provisioning and operational APIs matter even when the flight radio is working. DoorDash announcement.

9. Questions to send to shortlisted suppliers

Which exact aircraft and terminal configurations have you tested, with which frequencies, firmware versions and jurisdictions?
What share of our proposed route and hours is supported by measured application-level C2 availability? Supply the raw logs.
Who is responsible for lost-link behavior, bearer selection and safety-case evidence at each system boundary?
What happens to commands and telemetry after a failover; how are stale messages identified?
What is included in the managed service—terminal inventory, provisioning, dashboards, trouble tickets, API access, data retention and billing?
How can we export all logs and migrate terminals or fleet records at contract termination?
Which services are subcontracted, what are the support escalation paths and how are multi-party outages diagnosed?
What are the costs at our minimum, target and surge flight volume, including failed flights and aircraft held out of service?

These questions can be added to the broader complete UAV system RFQ template and cross-checked against the commercial delivery systems procurement checklist.

10. Buyer checklist and editorial conclusion

A serious BVLOS communications purchase is an integrated aviation, software and managed-service procurement. Acquire proof that the link works for the aircraft’s defined mission; that its failure is managed safely; that operational records can be reconciled; and that ongoing service costs match utilization. The supplier’s commercial launch, extensive partner ecosystem or global satellite footprint may reduce implementation friction, but none replaces local operating authority and route validation.

For related spectrum and interface considerations, read our FCC UAS connectivity review and November UAS radio planning guide. The regulatory discussion is general procurement context, not a representation that a particular system is compliant.

Primary sources and further technical reading

Editorial disclosure: UAVPackage.com is an independent informational site. Company mentions are descriptive, not endorsements. This article is not a solicitation response, safety approval, legal advice, or an offer to sell aviation connectivity services.