GNSS interference detection and mapping

Persistent RF monitoring from orbit turns GNSS interference from a rumour into a mapped, timestamped operational picture. This page covers what gets built, what it costs in relative terms, and what it cannot do.

The dependence this ends: Learning about jamming from airline incident reports

You are reading airline PIREPs as intelligence. That is the problem.

Since 2022, GNSS jamming has moved from a nuisance documented in aviation safety reports to a persistent operational condition across multiple regions. The Baltic approaches, the eastern Mediterranean, the Black Sea corridor and parts of the Middle East now see interference events that last hours, cover thousands of square kilometres and affect not just aviation but maritime navigation, precision agriculture, timing infrastructure and military positioning. Most governments learn about these events after the fact, from pilot reports, from port authorities, or from allies who happen to have monitoring assets nearby.

That is not an intelligence posture. It is an absence of one. The post-2022 environment has sharpened this: jamming is now used deliberately to degrade situational awareness before and during kinetic events, and spoofing, which pushes false position solutions rather than simply denying them, is harder to detect from the ground and harder still to attribute. A government that cannot map interference over its own territory cannot defend the infrastructure that depends on GNSS timing, cannot hold anyone accountable, and cannot give its own armed forces a reliable picture of the electromagnetic environment.

What the payload actually measures, and what it cannot.

An RF signal-mapping payload in low Earth orbit carries a wideband receiver tuned to the GNSS L-band frequencies (primarily L1 at 1575.42 MHz and L2 at 1227.60 MHz, with some missions extending to L5). As the satellite passes over a region, it records signal power, carrier-to-noise density and, where the payload includes a software-defined radio with sufficient processing, it can flag anomalous signal structures consistent with spoofing waveforms. The satellite's own precise position and timing, derived from an onboard GNSS receiver cross-checked against ground truth, allows the interference to be geolocated to a ground footprint.

The limits are real and worth stating plainly. A single satellite in inclined LEO revisits any given point roughly once every ninety minutes to several hours depending on orbital inclination and altitude, which means fast-moving or short-duration jamming events can be missed entirely. Geolocation accuracy from a single satellite pass is typically on the order of several kilometres without time-difference-of-arrival from a second platform. Cloud cover does not affect RF collection, which is an advantage over optical missions, but ionospheric conditions do introduce measurement noise. A pathfinder satellite gives you a statistical map of where interference tends to occur. It does not give you a real-time alert within seconds of a jammer switching on. That requires a constellation.

The ambition ladder: from first data to persistent coverage.

A pathfinder mission, typically one to three 6U cubesats in inclined LEO carrying RF signal-mapping payloads, establishes national collection capability and produces the first sovereign interference map. Small-satellite missions of this class have publicly reported budgets in the low tens of millions of dollars, with programmes such as HawkEye 360's early cluster providing a public reference point for what a small commercial RF-mapping constellation costs to initiate. Timeline from contract to first data is typically eighteen to thirty months, depending on payload heritage and launch availability. The output is a baseline: a historical record of interference events over national territory and approaches, processed into heat-maps and anomaly reports.

An operational constellation of six to twelve satellites in coordinated inclined LEO planes reduces the revisit gap to under thirty minutes over most latitudes and enables time-difference-of-arrival geolocation between satellites, improving emitter location accuracy significantly. This is where the mission transitions from monitoring to alerting: a ground system receiving downlinked data from multiple passes per hour can push interference notifications to air traffic management, maritime authorities and military operations centres within a tactically useful window. The constellation scale is comparable to early national RF-monitoring programmes and sits in a cost class that requires a dedicated national programme budget rather than a discretionary line item. Governments that have invested in GNSS augmentation systems, such as Japan's QZSS programme or India's NavIC, have demonstrated that sovereign positioning infrastructure at the constellation level is a multi-year, multi-hundred-million-dollar commitment; an interference-monitoring constellation is a smaller but structurally similar undertaking.

There is no full sovereign programme level for this mission in the sense of building your own GNSS constellation. The mission is monitoring, not provision. The ceiling is a persistent, multi-satellite alerting network with sovereign ground infrastructure and trained national operators.

What the customer owns at handover.

Ownership terms are agreed before signature. The customer receives the satellites, the ground station hardware and software, the mission control system, the interference-detection algorithms (with source access), the processed data archive and the trained operator team. Satellize does not retain a back door to the ground system, and the customer is not dependent on a continuing commercial data subscription to access their own collection.

What remains with Satellize or integration partners after handover is launch-vehicle relationships (rockets are arranged and integrated, not manufactured by Satellize) and, where the customer chooses it, ongoing algorithm updates as new jamming and spoofing waveforms emerge. That is a support contract, not a dependency: the customer can operate without it. The honest limit here is that interference detection algorithms require periodic retraining as adversaries adapt their waveforms. A government that does not invest in that ongoing capability will find its detection rates degrade over two to four years as jamming techniques evolve.

Why this mission is growing faster than almost any other RF application.

Before 2022, GNSS interference monitoring was largely an academic and aviation-safety concern. The ITU's Radio Regulations protect GNSS frequencies, but enforcement requires evidence, and evidence requires collection. The sharp increase in deliberate, large-scale jamming documented across European airspace since early 2022, combined with the emergence of spoofing events that pushed false position solutions into commercial aircraft navigation systems over the eastern Mediterranean, has changed the political calculus for procurement committees that previously saw this as a niche capability.

There is also a timing-infrastructure dimension that is easy to underestimate. GNSS is the timing backbone of mobile telecoms networks, financial settlement systems and power-grid synchronisation. A jamming event that is invisible to a government's monitoring infrastructure is not just an aviation hazard; it is a potential attack on critical national infrastructure with no forensic trail. The ability to produce a timestamped, geolocated record of interference events is the foundation of both defensive response and diplomatic or legal accountability. No other collection method provides that record at national scale with sovereign ownership of the data.

What this mission is built from

RF signal-mapping payloads: Primary sensor: wideband L-band receiver that records signal power and carrier-to-noise anomalies consistent with jamming or spoofing waveforms on each overpass.
GNSS radio-occultation payloads: Secondary payload option: provides ionospheric calibration data that improves the accuracy of interference measurements by separating atmospheric noise from genuine RF anomalies.
6U CubeSat platforms: Satellite platform for pathfinder and early constellation satellites: low unit cost and short build cycle allow first data within eighteen to thirty months of contract.
Inclined low Earth orbits: Orbital regime that maximises ground-track diversity over mid-latitude territories and approaches, reducing revisit gaps and enabling time-difference-of-arrival geolocation between constellation members.

What you end up owning

Flight hardware: the satellites themselves, with full title transfer at launch or on-orbit acceptance as agreed
Ground station hardware and software, including mission control system and data downlink infrastructure
Interference-detection and mapping algorithms, with full source access under terms agreed before contract signature
Processed data archive: all historical interference observations collected over national territory
Hardware audit rights throughout the programme, not just at handover
Trained national operator team, qualified to conduct independent mission control and data processing
Spectrum coordination documentation and ITU filing records associated with the mission

Handover is staged across the operational phase rather than delivered as a single event: national operators shadow Satellize mission controllers from first light, taking primary responsibility progressively as competence is demonstrated. At programme completion, Satellize retains no operational role unless the customer elects a separate support contract for algorithm updates. Launch-vehicle and some bus-platform relationships remain with integration partners, but these are disclosed at contract stage and do not affect the customer's ability to operate the mission independently.

Programme parameters

Pathfinder configuration	1 to 3 satellites, single inclined LEO plane
Operational constellation	6 to 12 satellites, multiple inclined LEO planes
Orbital altitude (typical)	450 to 550 km LEO
Revisit (pathfinder, mid-latitudes)	Approximately 90 minutes to several hours per point
Revisit (6-satellite constellation, mid-latitudes)	Under 30 minutes over most of national territory
Geolocation accuracy (single satellite)	Several kilometres; improves to sub-kilometre with time-difference-of-arrival across two or more satellites
Pathfinder timeline (contract to first data)	18 to 30 months, subject to launch availability
Operator team to sustain mission	4 to 8 trained national operators for a pathfinder; 10 to 20 for a full constellation with 24/7 alerting
Primary sensing frequencies	GNSS L1 (1575.42 MHz), L2 (1227.60 MHz), optionally L5 (1176.45 MHz)
Weather dependency	None: RF collection is unaffected by cloud cover; ionospheric conditions introduce calibration noise managed by occultation payload data

Sources

One contract, one accountable engineer

Commissioned as one programme, not a stack of contracts: spacecraft, launch, ground segment, mission control, training and handover are priced together. Source-access terms and audit rights are agreed in writing before signature. Request a pathfinder scoping session.