In 2024, a nationwide AT&T outage disrupted emergency communications, and affected access to 911 services in the US. More than 25,000 attempts to reach 911 were blocked, and service was disrupted for more than 125 million devices. At the same time, multi-state 911 outages continue to occur. Increasingly, for emergency response, the issue is not just whether networks are available, but how they perform when conditions change.

For the teams responding to calls or disaster events, working with real time video, data, and mobile command environments as part of day to day operations brings a different kind of pressure. Coverage alone is no longer enough; what matters is whether the connectivity remains usable under pressure, across networks, locations, and conditions.

Operating across multiple networks such as FirstNet or commercial LTE, traditional satellite, and increasingly LEO services such as Starlink introduces new complexity and inefficiency. Those issues now need to be addressed if emergency teams are to stay reliably connected.

 

Why Performance Matters as Much as Coverage

You can have a strong signal and still struggle to get the performance you need. During major incidents, networks rarely fail completely; congestion builds, latency increases, packets drop, and throughput becomes inconsistent. Even with signal present, performance becomes unpredictable. The FCC has highlighted how disasters expose these types of resilience gaps.

At the same time, operational demands are increasing. With the transition to Next Generation 911 (NG911), video, images, and real time data are becoming part of standard workflows. If communication links drop, the result is video feeds that struggle to stay stable; slower or unreliable access to CAD and GIS systems; and inconsistent performance between vehicles, command posts, and field teams.

Multiple networks: LTE, 5G, LEO satellite, and legacy GEO systems, are often all in play, whether by design or through gradual adoption. And this reflects a broader shift. Managing multiple technologies and networks is now part of the operational reality. So the challenge isn’t whether there is enough connectivity. It’s how well those networks work together when it matters.

Email-Multipath-5 Emergency services

Why Failover Based Connectivity Can Fall Short

Many setups still rely on failover. One network is primary, and others act as backup. It works when a network drops completely. It doesn’t work as well when performance degrades. In most incidents, what you actually see is:

  • Increasing latency
  • Packet loss
  • Reduced throughput
  • Unstable performance.

But failover only responds once a threshold is crossed, and by then, performance has already dropped below what applications need. There’s a delay between degradation and recovery, and during that time, services like video, VoIP, and real time data are disrupted.

It also means you’re not making full use of the networks available to you. Failover reacts to failure. It doesn’t actively optimize performance, which is the key.

Adding Starlink or Multiple Networks Doesn’t Solve the Problem Alone

You may already have addressed coverage gaps by adding services like Starlink. That improves reach and bandwidth, especially in remote or hard to cover areas. But adding more networks introduces its own complexity: multiple providers and contracts, different data plans and cost models, networks with very different performance characteristics.

Without coordination, those networks sit alongside each other, rather than working together. This often leads to manual switching between connections; static rules that don’t reflect real time conditions; uneven data usage across devices, and limited visibility into what’s actually happening across the whole response setup. So while you have more connectivity available, it’s not always being used in the most effective way.

What Multi-Network Connectivity Should Look Like in Practice

The shift here is not about adding more. It’s about changing how you use existing services, managing continuous, multi-network connectivity. In practice, that means multiple connections active at the same time and traffic routed dynamically based on real time conditions.

Instead of waiting for a connection to fail, the system adapts continuously, using the most appropriate network path at any given moment, based on latency, packet loss, and bandwidth. This is the principle behind Dejero Smart Blending technology, which routes traffic across multiple connections in real time rather than switching between them.

The outcome is more consistent performance, with fewer connectivity interruptions and less need for manual intervention. Making reliability less about network uptime, and more about service usability. It supports the wider move toward IP-based emergency communications, where video, data, and voice increasingly need to work across different networks and locations. And supports what matters most: not the status of one link, which is still important, but whether the overall service remains usable and effective at all times, providing true resiliency.

How Ground Control Multipath Optimizes Connectivity

Ground Control Multipath is designed to help you bring all of your networks together into something that works as a whole. It builds on what you already have: your existing LTE and 5G connectivity, your current satellite services, including LEO and GEO, and additional capacity where it makes sense.

Those connections are then managed through a routing layer that continuously selects the most appropriate path based on real time conditions. From your perspective, that means less time managing networks individually, more consistent performance across devices and locations, shared data usage instead of isolated plans, and reduced reliance on manual failover. The goal is not to replace your existing setup; it’s to make it work more effectively as a system.

The Multipath and Dejero TITAN fit

Ground Control Multipath provides the overall solution. It’s designed around your operation, and brings your available networks together so they work more effectively as one. Dejero TITAN is the device that brings your connectivity together, helping to manage multiple live connections, ensuring a seamless switch between networks, or combining them where needed, making bandwidth usage efficient and reducing your costs. In other words, Multipath is the overall service approach; TITAN is the enabling technology that can deliver it.

What This Means for Your Operations

When your networks work together properly, you see more consistent performance across video and data services, even when individual networks degrade. You make better use of the connectivity you’re already paying for, with data shared and optimized across the deployment. And you gain confidence in how your systems will behave during an incident, not because networks don’t fail, but because your setup adapts when they do.

Most agencies now operate across multiple networks, whether intentionally or not. The next step is making those networks work together. So this is not about adding more connectivity, it is about improving how it’s used. Good coverage is no longer enough. What matters is consistent, usable performance when it matters most.

Ground Control Multipath Dajero

Review Your Current Connectivity Setup

If you want to make better use of the connectivity you already have, we can help. Our team offers a no cost review of your current setup to identify where performance can be improved and costs reduced. It’s a practical conversation based on how you operate today.

Complete the form or email us at hello@groundcontrol.com and we’ll get back to you within one working day.

Name
Privacy Policy

Maritime, aviation, and defense operations all depend on GPS for positioning, navigation, and timing. But, as our infographic highlights, that dependence comes with real risk: GPS is vulnerable to jamming and spoofing, and relying on it alone creates a single point of failure.

That risk is becoming harder to manage. Reported interference incidents continue to rise across key regions, including a 127% rise in Baltic incidents between Q1 and Q2 2025, more than 1,000 vessels affected in Sudan and the Red Sea in 2025, and 5,655 flights spoofed in the Nicosia FIR in July to August 2024.

Why Modern GPS Threats Demand More Than Anti-Jamming

For a long time, disruption was often discussed mainly as a jamming problem. However, attack methods evolve, and disruption can now shift rapidly between jamming and spoofing. These are not the same threat; jamming tries to deny the signal, whereas spoofing tries to deceive the receiver. A solution that focuses only on anti-jamming may still struggle when an attack alternates between blocking the signal and imitating it.

That’s why resilience has to be about more than signal protection alone. It has to be about maintaining a trusted source of positioning even when GNSS is disrupted, denied, or manipulated.

What A-PNT actually means

A-PNT is best understood as a resilience approach, not a single technology. As the infographic sets out, it adds redundancy, position cross checking, trusted timing, and operational continuity when GNSS alone cannot be relied on. A-PNT isn’t “one new signal replacing GPS”; it’s a broader strategy for reducing dependence on a single vulnerable source.

GPS alone is no longer enough; A-PNT solutions infographic

Where Iridium PNT fits

Iridium PNT supports a broader A-PNT strategy by providing a completely separate source of PNT, with zero dependence on GPS. That independence is critical. If a backup still depends on GNSS somewhere in the chain, it may inherit the same vulnerability. Iridium PNT operates as a wholly separate system, giving operators an independent source they can use when GNSS is disrupted or cannot be trusted.

It also brings a major security advantage: the signal is encrypted and authenticated. In practical terms, that makes spoofing exceptionally difficult, because the receiver is not simply accepting any signal that appears plausible; it’s validating a trusted source.

Why that matters operationally

In the real world, navigation resilience is defined by whether a system continues to deliver trusted data under pressure. That means operators need more than a warning that GNSS has been compromised. They need:

  • An independent source of position and timing
  • Confidence that the source itself is trusted
  • Continuity if infrastructure is damaged
  • A solution that works with the systems they already use.

RockFLEET Assured is designed for use in contested and high risk operating environments. Its architecture supports flexible installation, with compute power in the above-deck unit and cable runs of up to 100 meters. That means the unit can be installed away from the bridge in a discreet location, making it harder to identify, harder to interfere with, and harder to damage deliberately.

If a cable is cut or a unit is attacked, what matters next is whether visibility disappears immediately. RockFLEET Assured includes backup battery capability, allowing continued transmission for a period even after cable loss. That additional continuity can matter enormously in a live incident. Even limited continued reporting can preserve situational awareness, support response, and reduce the risk of going blind at the worst possible moment.

Another key strength is flexibility. RockFLEET Assured can be used with our chartplotter, with a customer’s own chartplotter, or integrated into wider bridge systems. That gives operators multiple options to adopt resilient PNT capability without being forced into a rigid operational model. For many customers, the easier a resilient system is to integrate into existing workflows, the more likely it is to be deployed effectively and trusted by crews.

GPS still plays a vital role, but it is no longer enough on its own

As jamming and spoofing attacks become more sophisticated, more deceptive, and more hostile, operators need more than detection. They need trusted alternatives, genuine independence from GNSS, interoperability with existing systems, and resilience that holds up in the real world.

A-PNT helps by reducing dependence on one vulnerable source. Iridium PNT strengthens that approach by providing an encrypted, authenticated, wholly separate, satellite-based PNT capability, and RockFLEET Assured makes that capability operationally useful: survivable, flexible, interoperable, and built for continuity under pressure. That is what modern navigational resilience looks like.

Talk to us about resilience in practice

To explore how RockFLEET Assured can strengthen navigation resilience in your existing bridge environment, get in touch with our team.

Complete the form, or email hello@groundcontrol.com, and we will respond within one working day.

Name
Privacy Policy

Water quality monitoring no longer sits at the edge of operational strategy. It’s at the center of regulatory exposure, public reporting, and engineering accountability.

Designing or managing remote water quality monitoring systems lays the foundation for data continuity, defensible timestamps, and structured reporting outputs that withstand regulatory scrutiny. Across the UK, the United States, and other regulated markets, compliance expectations are tightening. Monitoring systems must now deliver continuous data, auditable records, and structured exports suitable for regulator portals and public dashboards.

Satellite IoT plays a defined role in meeting this regulatory need. The right architecture for the job reduces reliance on intermittent or patchy cellular coverage and strengthens confidence in the data transfer. The result is not simply connectivity; it’s system resilience and credibility.

Here we explore two remote water monitoring examples, and what they show about building confidence in the audit trail that follows.

How Regulatory Pressure is Reshaping Monitoring Design

In the UK, the Environment Act 2021 introduced statutory duties around monitoring upstream and downstream of storm overflows and sewage disposal works (Section 82). The UK’s storm overflow policy guidance outlines expectations for monitoring and transparency. Following on in 2023, environmental penalties in the UK were uncapped, removing the previous £250,000 ceiling for serious breaches. Enforcement activity has since reflected this increased accountability.

In the United States, the Clean Water Act operates through the National Pollutant Discharge Elimination System (NPDES). Submitting Discharge Monitoring Reports (DMRs), and reporting violations contribute to the Significant Noncompliance status. In summary, regulatory frameworks are established; what continues to evolve is their technical implication.

Water 1 Water Regulation Timeline

How Water Monitoring Systems Support Regulatory Standards

Water-Icon-1Continuous Data capture

Continuous or near-continuous data capture

Sensors record measurements at defined intervals, creating a consistent stream of operational data.

Water-Icon-2

Time stamped, immutable records

Each measurement is stored with a secure timestamp, preserving a verifiable historical record.

Water-Icon-3 Documented behaviour record

Documented uptime and connectivity behavior

The system logs device status and communication performance across the monitoring lifecycle.

Water-Icon-4 Secure Data Retention

Clear traceability and secure data retention

Collected telemetry is stored in protected systems designed to preserve operational and compliance records.

Water-Icon-5 Technical integration

API export capability for regulator integration

Monitoring data can be programmatically exported into reporting, compliance, and regulatory systems.

Why Connectivity Determines Confidence

Many remote river gauges, reservoirs, and discharge sites sit outside reliable cellular coverage. Even where coverage exists, service continuity can degrade during extreme weather, power disruption, or infrastructure failure. Total reliance on cellular connectivity introduces exposure.

Satellite IoT addresses this constraint directly. Low Earth Orbit (LEO) networks provide global coverage without dependence on local infrastructure. While satellite is not the right fit for every data profile, it offers coverage certainty where terrestrial networks cannot.

For message-based telemetry, Iridium Short Burst Data (SBD) supports low latency, small payload messaging suited to alarms, status updates, and exception-based reporting. That makes it particularly relevant where compliance-related events need to be captured and transmitted reliably from remote locations.

In practice, resilient remote monitoring often combines connectivity approaches to balance immediacy, scale, and power constraints. The examples below show what that can look like in water utility operations.

RockBLOCK-RTU-Diagram-Reservoir-Case-Study

Case Study 1: Reservoir Monitoring and Remote Pump Control

 

The first example involves a remote reservoir that requires dependable monitoring and controlled pump activation despite unreliable cellular coverage. Two RockBLOCK RTUs were installed.

The upper unit measures water level and flow. It operates outside cellular range and uses Iridium SBD to transmit short command and status messages. When the water level is sufficient, it signals the lower RTU to activate the pump.

The lower RTU actuates the pump and sends a periodic cellular heartbeat to confirm system availability, providing near-real time confirmation of upstream conditions, controlled pump activation, documented event timestamps, and independent verification of site status.

From a compliance perspective, the Cloudloop platform retains a time sequenced record of level measurement, command transmission, pump activation, and heartbeat confirmation. Therefore, if questioned, the operational timeline can be reconstructed.

RockBLOCK-RTU-Diagram-River-Level-Velocity-Case-Study

Case Study 2: River Health Monitoring With Micro Data Logging

 

In our second deployment example, a local water authority needed to measure river level and velocity, derive discharge, and capture core water quality indicators. Rather than installing a full stand-alone data logger with integrated satellite comms, RockBLOCK RTU’s micro data logging capability was used to capture essential metrics.

Thresholds were configured so sudden turbidity spikes or abnormal conductivity shifts triggered alerts. Measurements flowed directly into the connected software via Cloudloop API integration.

This approach provided continuous, time-stamped records, exception alerts to support rapid investigation, structured export into mapping and reporting tools, and reduced integration overhead. For remote water monitoring more broadly, logging infrastructure and communications layers remain unified rather than fragmented across separate systems.

Building an Auditable Data Pathway

Confidence in remote water quality monitoring doesn’t come from a single device, but from the integrity of the whole data pathway. When time stamps are preserved across each layer, transmissions are acknowledged, and configuration changes are logged, reliance on manual consolidation falls, reducing errors and saving both time and money.

Diagram showing the data pathway facilitated by RockBLOCK RTU

 

Auditability Across the Monitoring Chain

Within the layered architecture described above, the platform layer is where telemetry becomes a structured operational record.

Cloudloop Data provides the ingestion and decoding layer between satellite transmission and operational systems. Messages received from RockBLOCK RTU are converted into readable sensor values, normalized, time stamped, and made available through a secure portal or API.

This removes the need to manage raw payload parsing internally and helps ensure each transmission is logged with the metadata needed for traceability, including device identity, transmission time, and delivery status.

In the reservoir monitoring example, level measurements, command triggers, and pump activation confirmations are preserved as a time-sequenced operational record.

In the river health deployment, turbidity and conductivity alerts are decoded and logged with consistent metadata before export into reporting and GIS tools.

Cloudloop Data Decoded Screenshot

Visualizing and Integrating Monitoring Data

Cloudloop Insights builds on that structured data foundation by providing visualization, threshold configuration, and remote device control. Dashboards show both live and historical values, while threshold breaches, device status changes, and configuration updates are retained as part of the operational record, helping link system behavior back to defined monitoring parameters.

Both Cloudloop Data and Cloudloop Insights expose APIs, allowing telemetry and control data to flow into regulator submission tools, GIS environments, enterprise asset management systems, and custom EMS platforms. This API-first approach supports automated export for NPDES or UK reporting workflows, structured integration with mapping systems, programmatic access to historical telemetry, and closer alignment between remote measurement and institutional record-keeping.

Cloudloop Data Insights Screenshot

As remote water quality monitoring comes under greater regulatory scrutiny and public visibility, monitoring systems need to support continuous measurement, structured reporting, and reconstructable data lineage across distributed, infrastructure poor environments. Together, these examples show how message-based satellite telemetry, edge logging, and structured platform integration can support compliance-grade monitoring.

Can we help?

If you are reviewing or upgrading a remote monitoring architecture, our Technical Solutions team can help assess site conditions, regulatory obligations, sensor requirements, latency needs, and audit trail completeness.

Complete the form or email hello@groundcontrol.com and we’ll get back to you within one working day.

Name
Privacy Policy

Given that 90% of international trade is carried by sea, maritime safety is fundamental. For most of the modern maritime era, the formula was relatively simple: assess the route, understand the threat environment, adapt operating procedures, and, when justified by risk, place experienced personnel on board to deter, respond, and protect. That approach still matters, but it is no longer sufficient.

Today, merchant shipping is delegating a far broader range of responsibilities to private maritime security companies (PMSCs). The remit is no longer limited to protection from physical threats; increasingly, it also includes support for the operational risks created by disruption to critical onboard systems. One of the clearest and fastest growing examples is navigation resilience.

For maritime security providers supporting secure fleet operations, advising owners and operators, and delivering risk-managed transit, this change is already taking shape in practice. Clients may not use the term “A-PNT” (Assured Position, Navigation, and Timing), and they may not explicitly ask for “navigation resilience”. But the expectation is there nonetheless: in the questions they raise, the incident reporting they request, and the operational standards they increasingly assume are in place. The reason is straightforward: when positioning fails at sea, it becomes a security issue whether anyone labels it that way or not.

Security Has Expanded Beyond the Physical

The biggest misconception in maritime security right now is thinking this is a niche technical issue, something for bridge teams, electronics specialists, or a ship’s IT provider, when in practice, it has become a frontline operational risk.

GNSS disruption, jamming, and spoofing are no longer rare anomalies confined to active conflict zones. Independent analysis by C4ADS has documented widespread maritime spoofing events affecting thousands of vessels, particularly in the Black Sea and the Middle East. Subsequent advisories from the U.S. Coast Guard Navigation Center (NAVCEN) and UK Maritime Trade Operations (UKMTO) have continued to warn of GPS interference affecting commercial traffic in multiple regions.

When a vessel loses trustworthy position and timing, the impact cascades fast. Routing decisions become uncertain, safety margins shrink, bridge teams hesitate, and in high consequence waters, uncertainty becomes vulnerability. That’s why navigation resilience is moving into the security deliverables category. Not because it’s a buzzword, but because the outcomes are security outcomes – the ability to maintain control, continuity, and confidence in the vessel’s movements. And, as shipping companies continue to lean on third party providers to manage risk, the responsibility is naturally shifting to the people who already own the security mission.

 

Merchant Shipping Is Outsourcing Resilience, Not Just Risk

The International Maritime Organization (IMO) has formally recognized navigation systems as part of a vessel’s cyber risk surface. U.S. Department of Transportation reporting on Complementary PNT strategies has likewise acknowledged the vulnerability of civil GPS and the need for resilient alternatives. At the same time, the operational picture has become harder to ignore. From spoofed coordinates linked to tanker incidents, to cargo vessels disappearing from satellite tracking under jamming conditions, interference with positioning and navigation is now a live operational issue.

That has direct implications for maritime security. It is no longer enough for PMSCs to track piracy patterns and regional instability. They now have to understand electronic disruption, degraded communications, cyber-enabled interference, and deliberate manipulation of navigation systems. The threat landscape is no longer confined to the physical domain; it now extends into the systems vessels rely on to operate safely.

GPS Jamming map

For shipping companies, the response is familiar. When risk grows faster than internal capacity, they outsource. First that meant physical protection. Then it meant intelligence and route advisory. Now it increasingly means outsourcing resilience, especially where failure has immediate operational consequences. Navigation is one of the clearest examples.

The New Scope of PMSCs

PMSCs are increasingly being drawn into questions that would once have remained strictly on the bridge:

  1. What happens if GNSS becomes unreliable mid-transit?
  2. How quickly can we detect spoofing versus simple signal loss?
  3. How do we keep the bridge team confident in the vessel’s position when the primary reference is compromised?
  4. What proof can we provide after the fact – to the owner, to insurers, to regulators, and to internal stakeholders – that the vessel maintained safe navigation?

 

These are no longer theoretical or hypothetical concerns and possibilities; they’re operational questions and sit directly inside the modern security mission. Marine insurers and P&I clubs such as Allianz and Gard have already published guidance highlighting navigation system vulnerabilities as emerging operational risks. The Nautical Institute’s Mariners’ Alerting and Reporting Scheme (MARS) has also captured incident reports reflecting confusion and degraded situational awareness linked to navigation system anomalies. In many cases, the crew onboard is highly competent but not equipped with the tools or the time to manage GNSS integrity issues in a repeatable way. But it’s not a training failure – it’s an equipment and process gap.

 

Why A-PNT Is Becoming the Navigational Standard

The real challenge in modern navigation is not only loss of signal, but loss of trust. In a disrupted environment, the greatest risk is often not that positioning disappears, but that it appears reliable when it is in fact wrong. That is what spoofing does, and it turns navigation failure into an operational and security problem.

That’s why A-PNT is becoming increasingly important. It’s often not a single product or platform, but a broader resilience approach: ensuring that positioning, navigation, and timing remain dependable and verifiable when GNSS is degraded, denied, or manipulated.

Solutions such as Iridium PNT sit within that broader picture. They offer an additional means of maintaining trusted PNT in operating environments where traditional GNSS may be vulnerable to interference.

For maritime operators, that is the real shift. A-PNT is becoming less of a specialist capability and more of an operational standard, because resilience in navigation is increasingly inseparable from resilience in the voyage itself.

GPS-RockFLEET-Assured-Diagram

Where RockFLEET Assured Fits into Modern Maritime Security

RockFLEET Assured, powered by Iridium PNT, enters the market at a moment when PMSCs are increasingly expected to provide resilience as part of secure fleet operations, not just protection from physical threats.

 

Designed specifically for maritime deployment, the marine-grade smart antenna delivers cryptographically authenticated positioning and an assured navigation reference for vessels operating in environments where GNSS integrity cannot be guaranteed. In practice, that means an independent source of trusted position data when GPS or other GNSS signals are degraded, denied, or manipulated.

Its value is operational as much as technical. By comparing GNSS inputs with Iridium PNT outputs, RockFLEET Assured helps bridge teams and shore-based personnel identify anomalies more quickly, detect possible spoofing or jamming, and respond with greater confidence. Event data can be logged and transmitted ashore, creating a defensible record for incident review, compliance documentation, or insurer scrutiny.

RockFLEET-Assured-Installation-Transparent-BG

Just as importantly, it’s built for repeatable deployment at fleet level. The system is delivered as a single above-deck terminal, with mounting options to suit different vessel types and superstructure layouts, reducing the need for vessel-by-vessel customization. Its IP66-rated enclosure is designed for exposed marine conditions, and no below-deck electronics are required unless bridge view is selected.

RockFLEET-Assured-on-Map-Plotter

Reporting is equally flexible. Through Iridium Messaging Transport (IMT), RockFLEET Assured supports configurable position updates and secure two way messaging between ship and shore, with reporting intervals tailored to different operational requirements. Integration with Ground Control’s Cloudloop platform enables centralized fleet visibility, while API connectivity supports incorporation into existing monitoring and security systems.

Optional bridge view functionality adds another practical advantage, allowing assured positioning data to be displayed alongside standard GNSS outputs. For crews, that provides a clearer visual reference during interference events and helps reduce hesitation when rapid navigational decisions are required.

For PMSCs, that makes RockFLEET Assured a practical way to embed navigation resilience into a broader security offering. Rather than treating disruption as a vague technical failure, it helps turn it into something observable, reportable, and manageable.

What Changes Operationally for PMSCs

PMSCs often operate under heightened expectations for compliance, documentation, and professionalism. Clients – corporate security teams, fleet operators, insurers, charterers – expect measurable capability, not procedural reassurance. Without A-PNT, disruption remains ambiguous. With it, disruption becomes detectable, documentable, and defensible. That shift strengthens operational reporting, reduces decision latency on the bridge, and improves client confidence. It becomes a deliverable in a security modeland part of how PMSCs define secure fleet operations in 2026 and beyond.

The Future of Maritime Security

The maritime security industry is not abandoning its roots: physical threats still exist, high-risk areas still demand proven experience, and human expertise still matters. But the center of gravity is shifting as electronic disruption, contested signal environments, and hybrid risk become normalized features of global shipping lanes. International policy bodies, insurers, and national governments have all acknowledged this reality in recent years.

The most forward-looking maritime security providers are therefore evolving from personnel-based security offerings to layered security and resilience platforms. They are expanding into technical advisory, electronic threat awareness, and operational continuity support. They are positioning themselves as secure fleet partners, not just voyage contractors, and A-PNT is one of the cleanest, most valuable additions to that stack.

The next era of maritime security will be defined by who can keep ships operating safely and confidently when the environment becomes contested physically, electronically, and operationally. Navigation resilience is becoming a security standard because disruption is becoming the norm, so for PMSCs responsible for secure fleet operations, this is the moment to lead. The companies that adopt assured A-PNT now through solutions like RockFLEET Assured will be the ones positioned to define what security means at sea over the coming years or more.

Trusted A-PNT For Navigational Certainty at Sea

For over 20 years, we’ve delivered resilient satellite solutions for remote connectivity and secure communications. We’re proud to support commercial shipping, offshore operators, and maritime security providers with dependable satellite connectivity and assured positioning capabilities designed for the realities of the modern maritime domain.

If you want to offer A-PNT solutions as part of the security strategy for your maritime clients, complete the form, or email hello@groundcontrol.com and we’ll reply within one working day.

Name
Privacy Policy

Operating beyond cellular coverage is a reality for many ArduPilot-powered vehicles, and satellite is often the only practical backhaul. Recently, the ArduPilot Development Team (with support from Ground Control) documented MAVLink telemetry performance over Iridium Certus 100 using the RockREMOTE UAV OEM modem. The goal: understand what usable telemetry looks like over a real satellite link, and share configuration guidance the community can replicate.

RockREMOTE UAV OEM is a low SWaP Certus modem designed for OEM integration on unmanned aircraft. It provides an IP data path for BVLOS command and control (C2), MAVLink telemetry, and payload/edge networking when terrestrial backhaul isn’t available.

What the ArduPilot testing looked at

The work, conducted and written up by Stephen Dade, a member of ArduPilot’s Development Team, evaluated MAVLink telemetry reliability and latency over Iridium Certus 100 across multiple connection configurations. In the reported results, MAVLink telemetry was usable and consistent when configured appropriately, with typical round trip latency reported in the sub-2 second range.

Key takeaways from the write-up

  • Reliable MAVLink telemetry over Certus 100 (with the right config): The test summary reported measured latencies roughly in the ~600-1600 ms range, with broader observed ranges depending on protocol and conditions.
  • Stream rates matter under uplink constraints: The write-up notes Certus 100 uplink limits and recommends configuring ArduPilot stream rates around 2 Hz to stay within available throughput.
  • Secure connectivity works best when designed for satellite: High latency/low bandwidth links benefit from VPN patterns optimized for satellite. Ground Control supports architectures that terminate secure tunneling at the gateway, and offers WireGuard where on-link VPN is required.
  • Installation can make or break performance: Antenna placement and local obstructions (trees/buildings) had a major impact. Roof height mounting improved results versus a low height suburban placement.
RR-UAV-OEM-being-tested-with-ArduPilot

Why this matters for integrators

The documented setup used a representative unmanned systems stack (ArduPilot flight controller, Ethernet bridging, and ground endpoint infrastructure), and the notes are practical for anyone building satellite-enabled autonomy: you can design for predictable behavior, but you have to design around constraints like latency, throughput, and installation quality.

“These results help validate a satellite telemetry approach that can extend operations into truly remote areas, and provide the community with clear configuration guidance.” – Stephen Dade, ArduPilot Development Team

“What’s exciting here is giving builders real architectural choice: lean messaging for efficient telemetry, and IP connectivity when an uninterrupted C2 link matters.” – Alastair MacLeod, Ground Control CEO

Read the full technical write-up

The full methodology, recommended configurations, and measured performance data are here: https://discuss.ardupilot.org/t/ardupilot-and-the-iridium-certus-satellite-service.

Need help integrating Certus100 with ArduPilot?

If you’re looking at satellite-enabled ArduPilot telemetry using Iridium Certus 100, including hardware availability and integration guidance, we’re here to help.

Complete the form, or email hello@groundcontrol.com, and we’ll connect you with our drone specialists within one working day.

Name
Privacy Policy

Plus, How to Create Long Term Monitoring Stability

Remote environmental monitoring systems rarely fail all at once. Performance erodes gradually; data gaps widen, devices fall offline intermittently, power budgets tighten, and maintenance intervals shrink. Over time, reliability drops below what the original design assumed. The infographic below summarizes the most common technical and operational factors behind that decline, based on long term field observations across utilities and remote environmental monitoring deployments.

Many of these patterns may be familiar to you, yet their cumulative impact over five to ten years is less visible. Long term degradation is typically captured in post-mortems, warranty data, and support logs rather than formal reporting, so systemic reliability issues are often inferred from truck rolls or unexplained data loss instead of addressed at the design stage. Connectivity selection, power design, enclosure strategy, and remote management capability all shape lifecycle performance. Understanding these failure modes helps frame more durable trade-offs early, particularly where hybrid cellular and satellite options are being considered.

Why remote environmental sensing projects fail infographic

 

Helping OEMs Choose

For sensor OEMs, long term reliability increasingly shapes product selection and channel acceptance. Coverage variability, power constraints, integration overhead, and regulatory requirements all influence whether satellite or hybrid connectivity is commercially viable within your portfolio.

Our Environmental Sensor OEM connectivity guide outlines practical integration models, device classes, lifecycle considerations, and where satellite and hybrid designs materially reduce field failure risk. It is structured to support internal technical and commercial evaluation.

View Guide
Environmental Monitoring. Sensor Brochure. Image of front cover.
EnviroBlog-Lifecycle-1 Image System degradation remote monitoring

Designing for Long Term Remote System Performance

If you’re designing for durable performance over the full deployment lifecycle of your remote environmental monitoring system, that means balancing coverage, power budget, data volume, enclosure design, remote management, and maintenance costs before scale amplifies weaknesses.

Satellite and hybrid architectures introduce different trade-offs depending on reporting frequency, firmware strategy, and site accessibility. Reviewing these options early helps reduce unplanned site visits and sustain data continuity over years, not quarters.

We’ve written more about this in our blog: Designing for Power and Reliable Data Delivery Under Uncertain Connectivity.

Find out more

If you are reviewing a current deployment or planning a new one, we can provide structured technical input based on your use case, power constraints, data profile, and coverage requirements. We design and manufacture our own devices and also support third party satellite hardware, so recommendations are aligned to lifecycle performance rather than a single product line.

If you complete the form with a brief outline of your application and constraints, a member of our engineering or technical support team will respond with impartial, practical guidance.

Name
Privacy Policy

Iridium have just announced that they’ll launch their latest satellite IoT transceiver, the Iridium 9604, in June 2026. We’re exploring how this differs from its immediate predecessor, the 9603, and its “big brother”, the Iridium Certus 9704 module.

What is the Iridium 9604 module?

Iridium 9604 is a satellite IoT transceiver that utilizes Iridium’s Short Burst Data (SBD) service to send small volumes of data from remote applications operating outside cellular coverage.

In addition to SBD the 9604 module can also transmit using LTE-M cellular connectivity, making it ideal for mobile applications that cross in and out of cellular coverage, or where cellular coverage is unreliable, so a satellite failover is beneficial. The device doesn’t force automatic switching; it’s up to application developers to enable either simple failover rules or more advanced routing logic.

The 9604 module also features integrated GNSS (multi-constellation: GPS/GLONASS/Galileo/BeiDou), making it well-suited for tracking as well as IoT applications.

What Applications are Suited to the 9604?

The new 9604 module is extremely small, measuring just 16 x 26 x 2.4 mm; the weight hasn’t yet been released but we can assume it will be similarly tiny. And while we don’t yet have detailed specifications,, Iridium have stated that it is designed for ultra low power applications.

Any mobile remote IoT application constrained by size, weight and power – e.g. drones/UAVs, animal tracking, data buoys, autonomous machinery – will benefit from the 9604’s form factor and dual-mode satellite/cellular capabilities.

How Does the 9604 Differ from the 9603 Transceiver?

  • Connectivity: the 9603N uses Iridium SBD (340 bytes transmit; 270 bytes receive), as does the 9604, however the 9604 also adds LTE-M connectivity.
  • Tracking: the 9603N needs to be paired with a separate GNSS receiver to transmit a location, whereas this capability is built into the 9604.
  • Form factor: the 9603N measures 31.5 mm × 29.6 mm × 8.1 mm vs. the 9604’s 16 x 26 x 2.4 mm.

Will it be Easy to Upgrade from 9603 to 9604?

We anticipate a lot of teams will want to keep their familiar SBD workflow, but add cellular opportunism. We will be available to help make this migration process simple. And for teams outgrowing SBD message sizes, we can help make the jump from SBD to IMT.

Iridium-9603N-vs-Iridium-9604-Module
Iridium-9604-vs-Iridium-Certus-9704-Module

How Does the 9604 Differ from the 9704 Transceiver?

Iridium relatively recently launched the Certus 9704 satellite IoT transceiver (December 2024), and the 9604 is not a direct competitor or successor to this device. 9604 is about hybrid connectivity for small messages, while 9704 is about bigger payloads.

The 9704 utilizes Iridium Messaging Transport (IMT), which will transmit up to 100 KB per message; up to the challenge of sending aggregated gateway data, audio, and compressed images. The 9604 uses Short Burst Data (SBD), which is intended for extremely small messages (340 bytes transmit / 270 bytes receive).

The 9704 module is larger – 31.5 mm × 42.0 mm × 3.8 mm – and does not have built-in GNSS or cellular capabilities; it is intended for fully remote deployments where you still need meaningful data volume.

Choose the 9604 if you’re sending small messages frequently; if you’ll benefit from its hybrid connectivity, and if your goal is optimized cost/performance in mixed coverage regions.

Which Devices Utilize the 9604 Transceiver?

We’re part of Iridium’s beta program, leveraging our decades of experience working with Iridium modules to build customer solutions that make it easy to benefit from the 9604’s extra capabilities – hybrid connectivity, low power consumption, and a tiny form factor.

Both the bare module and the Ground Control solutions will be integrated into Cloudloop, our cloud-based, API-first IoT platform which manages subscriptions, devices and data. Cloudloop Data is particularly useful for systems integrators, as it seamlessly routes uplinks and downlinks to your HTTPS or MQTT endpoint, and exposes a REST API and dashboard for device metadata, transmission status, and message history.

How to Get Started

We encourage you to contact us to discuss your application; we are Iridium experts, and will provide you with impartial advice on the best airtime, service and hardware to best meet your needs.

Fill in the form or email hello@groundcontrol.com, and we’ll reply within one working day.

Name
Privacy Policy

Global Navigation Satellite Systems (GNSS) such as GPS, Galileo, GLONASS, and BeiDou have driven navigation for Unmanned Aerial Vehicles (UAVs) for decades. These satellite signals provide critical positioning, navigation, and timing (PNT) data that inform core functions like waypoint navigation, path planning, dynamic obstacle avoidance, geofencing for airspace compliance, and failsafe behaviors such as Return to Home or auto landing. However, GNSS/GPS signals are inherently weak – designed to be received at the Earth’s surface from satellites tens of thousands of kilometers away – and as such, are vulnerable to interference, jamming, or deliberate PNT denial.

Particularly over conflict zones, but increasingly widespread, GNSS signals are being degraded, spoofed, or blocked, causing multipath errors and signal loss and leaving autonomous drones without reliable positioning or timing information. Reliance on GNSS alone subsequently becomes a single point of failure for safe, reliable and trusted and UAV operations.

This is why navigation resilience has become one of the most important technical and operational requirements for modern BVLOS UAV deployments, and why selecting the right navigation solution is no longer simply about accuracy, but about operational continuity, trust, and reliability when navigational conditions degrade.

In this blog, we’ll explore the satellite service that addresses GNSS/GPS overreliance, the onboard technology that delivers resilient UAV navigation in contested environments, and the key factors integrators should consider when choosing a navigation stack for BVLOS operations.

Continuity Challenges in Contested and Complex Environments

Studies on GNSS-denied navigation show that jamming can overwhelm genuine satellite frequencies, driving receivers into error or total loss of signal. Spoofing goes a step further by feeding convincing but false signals, tricking receivers into calculating an incorrect location and potentially sending autonomous systems off course. This isn’t theoretical – the mechanisms and impact of GNSS spoofing and jamming are well documented, with spoofing described as a more complex and deceptive threat than simple interference, because it actively misleads the navigator rather than just depriving it of data.

GNSS denial isn’t confined to military battlefields either. Complex civil environments present similar challenges. Urban canyons made of steel and glass can reflect, attenuate, and distort satellite signals. Industrial zones rife with electromagnetic activity can drown out weak satellite broadcasts. Remote farmlands, border regions, and mountainous terrain all produce signal shadows and multipath effects, and these are not edge cases; many operators encounter these conditions regularly.

Without trusted PNT, a drone’s ability to follow a flight plan, maintain orientation, and sense its environment becomes compromised. In military operations, this can mean the difference between mission success and failure when conducting reconnaissance, supply delivery, or coordinated swarm operations. In maritime environments far from land, relying solely on GNSS undermines situational awareness and safety. In these contested or degraded environments, drones that depend exclusively on GPS risk mission degradation, erratic navigation, or complete loss of control.

It’s worth noting, however, that when a UAV loses trusted PNT, it doesn’t necessarily lose the ability to fly. Rather, it loses confidence in where it is, and that uncertainty is enough to abort missions, degrade data quality, violate airspace restrictions, or erode operator trust. Without PNT, UAV missions fail not because the vehicle lacks propulsion or control, but because it cannot navigate with confidence. For BVLOS operations, this loss of confidence is especially critical. Unlike VLOS flights, BVLOS operations depend on automation, remote supervision, and regulatory compliance. A drone that cannot prove where it is – reliably and continuously – cannot safely remain in controlled airspace or operate near people, infrastructure, or other aircraft.

The Solution Beyond GPS

To address the vulnerabilities in GNSS/GPS, engineers and operators are turning to Assured Positioning, Navigation and Timing (A-PNT).

A-PNT represents a layered approach in which GNSS is complemented, and in some cases temporarily replaced, by alternative sources that can provide trusted PNT data in environments where GPS is unavailable or untrusted. One alternative A-PNT source is derived from Iridium, and broadcast from a constellation of Low Earth Orbit (LEO) satellites. Because these satellites orbit significantly closer to Earth than traditional GNSS satellites, the downlink signals are up to 1,000 times stronger and more resistant to jamming or obstruction.

What makes Iridium’s PNT particularly effective is also its hybrid operation. When GNSS signals are present and reliable, an A-PNT system can blend that positioning data with Iridium PNT to maximise accuracy. When GNSS fails or is compromised, the system can continue operating on the stronger, authenticated Iridium PNT signals alone, preserving continuity of service and trusted navigation. This redundancy is key for autonomous systems that cannot afford to lose their bearings due to interference or contested signals.

In addition, the Iridium PNT signal incorporates cryptographic authentication that enables receivers to verify the integrity of their navigation signals and reject spoofed or tampered data. Whether operating at sea, in urban canyons, or in warfare environments, A-PNT provides a resilient and secure source of position and timing that can help autonomous drones sustain operations when GNSS cannot be trusted.

Why Antenna Positioning Still Matters in GNSS-Denied Scenarios

Even before GNSS is intentionally denied, the physical realities of a UAV or drone’s design can degrade satellite reception. The placement and orientation of antennas determine how effectively a platform can see the sky and receive navigation signals.

Placement near high current electronics, motors, or carbon fiber structures can block signals and create multipath interference, both of which erode signal quality. In contested environments, where robust reception is already tenuous, such degradation only exacerbates the problem. Careful antenna placement – including optimal sky visibility, proper ground planes, and physical isolation from noisy subsystems – remains foundational to any navigation strategy that seeks resilience when GNSS signals are challenged or absent. Further, incorporating A-PNT sources into those antenna systems becomes essential to maintaining navigation and timing.

 

RockBLOCK APNT for Autonomous and UAV Platforms

One of the standout implementations of this A-PNT approach is RockBLOCK APNT – a rugged, self-contained satellite device designed to deliver Iridium PNT-based positioning data even in GNSS-denied environments. RockBLOCK APNT integrates both Iridium PNT and multi-constellation GNSS reception into a compact device suitable for integration with drones and other unmanned systems. By leveraging Iridium’s globally available, authenticated PNT signals, RockBLOCK APNT delivers a level of navigational assurance that GPS alone cannot provide.

For UAV manufacturers and integrators, A-PNT needs to be both practical and reliable. Built with an IP66-rated rugged enclosure, RockBLOCK APNT withstands harsh operational conditions across land and aerial deployments, making it suitable for military, industrial, and maritime applications where environmental stresses and contested RF conditions are common.

The design is also considerate of OEM deployment, featuring a compact form factor with low size, weight, and power (SWaP) requirements, and standard interfaces that simplify integration into existing navigation stacks. It is designed to be both resilient and flexible, supporting serial, USB-C, and Bluetooth connectivity, and easily configurable with common development tools.

Notably, the device also operates with twin antennas to optimize sky visibility and signal resilience according to the drone’s design. In addition to delivering trusted PNT data, RockBLOCK APNT also provides two way satellite messaging up to 100 KB, offering a valuable fallback communications channel when other links fail.

Drone-with-GC-Circles

For UAVs and drones operating BVLOS, the ability to compare GNSS and Iridium PNT data streams is a powerful tool for detecting anomalies indicative of interference or spoofing. By validating position and timing against independent sources and reducing dependence on a single satellite navigation source, RockBLOCK APNT enhances navigational integrity and situational awareness. Operating on stronger Iridium PNT signals also expands the envelope of reliable navigation to areas where traditional GNSS geometry is poor or disrupted, such as high latitudes or deep urban corridors.

 

Future-Proofing UAV Operations With A-PNT

GPS and GNSS have served the world of autonomous navigation well, but they were never designed with modern contested environments in mind. As threats evolve and operations push into regions of intentional interference or obstructed signal conditions, autonomous systems must adapt.

If GNSS is your only source of PNT, your unmanned platform has a single point of failure. In environments where GNSS signals can be jammed, manipulated, or unavailable, this reliance represents a significant operational liability.

A-PNT, powered by strong alternative signals such as Iridium PNT and delivered through devices like RockBLOCK APNT, offers a practical, resilient path forward. By blending multiple navigation sources and validating integrity through authenticated signals, autonomous drones can maintain reliable PNT and continue operating effectively, even when GPS fails.

RockBLOCK APNT delivers UAVs a trusted, independent, and resilient source of positioning, navigation and timing. This enables UAVs to maintain autonomy under interference, preserve mission continuity, protect critical timing and coordination functions, and operate globally with confidence.

Trusted A-PNT For Resilient UAV and Drone Operations

Ground Control brings more than 20 years of experience delivering resilient satellite solutions for remote connectivity and secure communications. We provide expert guidance on deploying the right mix of A-PNT capabilities and reliable satellite connectivity options to ensure trusted positioning, navigation, and for autonomous drones, aircraft and UAVs.

Complete the form, or email hello@groundcontrol.com and we’ll reply within one working day.

Name
Privacy Policy

Remote IoT looks straightforward until you hit the realities of variable latency, tight data budgets, and devices you can’t easily reach once deployed.

This free and ungated eBook distills the integration pitfalls Ground Control sees most often, plus the practical patterns that help teams go live faster and stay operational long after launch.

It’s written for IoT product and platform teams, systems integrators and solution architects, operations and field deployment leaders, and security/IT stakeholders supporting remote infrastructure.

Read Free eBook
Cover-of-Six-Costliest-Mistakes-eBook

What’s Inside: The Six Costliest Integration Mistakes

1. Security & IT Reality Checks

Satellite links can be strongly encrypted, but risk often concentrates at the handoffs, where data routes from the ground segment into your cloud / application environment.

The eBook outlines common postures (VPN + firewalls, private circuits, or higher-isolation architectures) and the blockers that derail projects late.

Fast takeaway: map the end to end path, choose the security posture deliberately, define ownership, and pre-empt IP range conflicts/timeouts before they become downtime.

Security-Mistakes-Remote-IoT
Interoperability-is-not-automatic

2. Interoperability Isn’t Automatic

Remote IoT punishes cellular assumptions. The economics change when every transmission costs power, airtime, and often money.

This chapter shows how teams avoid brittle integrations by designing around constraints: a minimal payload strategy, a clear send policy, and ingestion built for compact messages.

Fast takeaway: prioritize purposeful messages and treat the translation layer as critical infrastructure – version it, test it, and monitor it.

3. The Field Will Prove You Wrong

Coverage maps don’t guarantee performance. Antenna placement, terrain, structures, and foliage create real world RF failure modes.

The eBook clarifies the difference between ‘clear view of the sky’ (LEO satellites) and ‘line of sight’ (GEO satellites), and why confusing these leads to broken installs.

Fast takeaway: validate sky view at the true install height, and test in the actual environment before you scale.

Antenna-Placement-Issues
Design-for-Delays-not-Perfection

4. Design For Delays, Not Perfection

Message-based satellite IoT doesn’t behave like web or cellular. Systems fail when they assume instant confirmation and tight timeouts.

This chapter explains the ‘accepted vs delivered’ distinction and why retries, buffering, and correct acknowledgements are foundational.

Fast takeaway: use jitter + backoff, implement store and forward properly, and only return ‘success’ after durable storage.

5. Lifecycle and Remote Device Management

Remote device management traffic competes with mission data – reboots, logs, config reads, and updates all consume power and paid data.

The eBook covers how teams avoid slow-motion failures by separating ‘alive’ from ‘healthy’, controlling configuration drift, and planning staged updates.

Fast takeaway: treat configuration like code, budget for ops traffic, and design a real end of life workflow.

Lifecycle-Management-Challenges
Data-Discipline-Constrained-Connectivity

6. Data Discipline in Constrained Connectivity

Most systems can produce far more telemetry than anyone will ever use, and ‘send everything’ is the fastest way to lose control of battery life and budgets.

This chapter gives practical patterns like exception reporting, edge summaries, payload compaction, and ruthless prioritization so you protect what matters most.

Fast takeaway: define the smallest information set that drives decisions, then budget size/frequency/retry rules by priority tier.

Key Outcomes You Can Expect

By the end, you’ll be able to spot the integration choices most likely to cause schedule slip and rework, set realistic expectations for latency, delivery confirmation, and retries, and build payload and send policies that scale economically.

You’ll also learn how to reduce truck rolls by designing lifecycle management in from day one, and how to pressure test your deployment plan before you scale it.

The core theme throughout is simple: design for operations, not just installation.

Read the eBook before you make your next integration decision

Get the PDF immediately (ungated). It covers security handoffs, interoperability, field RF realities, latency/retries, device lifecycle, and data discipline.

Read Free eBook

Want help pressure testing your integration plan?

If you’re planning a remote deployment and want to validate your architecture, data budget, or rollout approach, we can help you identify risk early – before it becomes field rework.

Contact Our Experts

FAQs

Is this eBook only about satellite IoT?

It’s written for remote deployments where constraints matter most – satellite and hybrid deployments in particular – but the integration lessons apply broadly to any system where latency, cost, power, and field access are real constraints.

Will this help if we’re already live?

Yes. Several chapters focus on operational issues that appear after launch (retries, lifecycle management, configuration drift, and data discipline).

Does it include practical checklists?

Yes. Each chapter ends with concrete takeaways (e.g., security mapping and ownership, field testing non-negotiables, ‘slow link’ checklist, and data discipline checklist).

Have a remote IoT project to discuss?

No need to contact us to read the eBook – but if you want to chat about your remote IoT project, we’d love to hear what you’re working on.

Complete the form or email hello@groundcontrol.com with your application details, and we’ll connect you with one of our expert team to see if we can support your goals.

Name
Privacy Policy