Beyond Line of Sight: Designing Resilient Communications for Loitering Munitions and UAVs

As loitering munitions and UAVs move toward larger, more cost-sensitive fleets, beyond-line-of-sight (BLOS) communications become a platform-design decision. The link must support mission-appropriate command and control, fit strict size, weight and power limits, and remain resilient in contested environments. It must also give the customer clear control over how the network is managed and where traffic is routed.

Why the Link Belongs in the Design Review

A loitering munition or UAV operating beyond terrestrial coverage may need to receive a command, report telemetry or exchange mission data while jamming, surveillance and loss of GPS cannot be ruled out. The satellite link is part of the mission architecture, and it deserves the same level of attention as the airframe.

The pressure grows as defense forces explore lower-cost systems and higher-volume fleets. More airframes mean tighter unit-cost targets, simpler integration and less room for communications to surface as a late-stage program risk. Each platform needs a link that fits its mission, is available when required and is managed on terms the customer controls.

In our view, the satcom link should be specified early in the platform design process, alongside the airframe, power budget and mission requirements. Bringing communications into the design review from the outset helps avoid costly redesigns later and gives customers greater control over how their systems connect and operate in contested environments.

What BLOS Communications Must Deliver

Four engineering considerations shape the decision. The right balance depends on the platform, operating concept and required performance.

• Size, weight and power (SWaP). Every gram and watt competes with range, endurance and payload. Terminal size, antenna design, power draw, thermal needs and integration constraints should be assessed early, against the actual airframe budget.
• Low probability of intercept and detection (LPI/LPD). A functioning link can still create an unwanted signature. LPI/LPD design reduces the likelihood that transmissions are detected or exploited, keeping the platform harder to find. Evaluate it against the mission threat model.
• Resilience in contested conditions. Jamming, interference, changing satellite availability and loss of navigation inputs can all affect connectivity. Programs should examine how the complete system behaves during degraded conditions, including whether the architecture supports alternative paths or operating modes.
• Command-and-control performance. Throughput, latency, availability and continuity all matter for UAV command and control, and the required mix depends on the mission. Retargeting, telemetry and other data exchanges should be matched to the timing and reliability requirements of the specific platform.

GEO and LEO options, frequency-band choices and GPS-independent operation each contribute to a resilient architecture, and each should be matched to the mission profile, link budget, coverage, latency, interference environment and operational constraints.

Sovereignty Is an Architecture Decision

Procurement also turns on who operates the gateways, controls network management, provisions terminals and determines where traffic is routed. Ask these questions alongside the connectivity ones.

Commercial satellite services can provide valuable access to coverage, while dedicated military systems may address specific operational requirements. For programs that need greater direct control over network operations, a privately managed satellite network is another architectural option. The key is to evaluate the trade-offs explicitly: control, interoperability, resilience, deployment model, lifecycle cost and dependence on external providers.

HiSKY Private Satellite Networks are built around an integrated architecture of terminals, a HUB and the Space Control network management system (NMS). The NMS can run on customer premises, including on a stand-alone LAN or an air-gapped network, giving customers direct control over provisioning, link monitoring and network management, with traffic routed through their designated gateways.

HiSKY’s ForceLITE offering combines terminals with the HUB and Space Control NMS. The architecture supports GEO and LEO satellite connectivity, shared channels for fleet management and dedicated channels on demand. With thousands of terminals deployed worldwide, it is a fielded system that can be configured to the platform and mission.

We believe that deciding who controls the network early in the program helps avoid mismatches between operational requirements and the final deployment, particularly when customers need direct control over provisioning, traffic routing and network management.

Three Questions to Ask Before You Commit

• Will it fit? Assess terminal dimensions, antenna placement, power consumption, thermal management, interfaces and the effect on the platform’s payload and endurance.
• Will it hold the schedule? Look for a productized architecture, clear integration documentation, a realistic qualification plan and evidence that the supplier can support your milestones.
• Who controls the system? Clarify ownership and operation of the terminal, gateways and NMS; data-routing arrangements; third-party dependencies; export-control requirements; support obligations; and total cost across the fleet lifecycle.

Start From the Mission

No single BLOS architecture fits every UAV or loitering munition. The right choice depends on the mission, the airframe, the required C2 performance and the level of network control the customer needs. Start with those requirements, then compare the complete system: terminal, satellite access, gateways, network management, integration effort and lifecycle cost.

HiSKY brings together compact satellite terminals, a HUB and Space Control NMS in a privately managed network architecture. If you are weighing BLOS connectivity, bring your airframe’s SWaP budget and C2 timing requirements to the evaluation and see how that architecture maps to them.

PLANNING A BLOS-ENABLED UAV OR LOITERING MUNITION?

Evaluate terminal integration, C2 requirements and network architecture with HiSKY.

hiskysat.com | info@hiskysat.com