RF intelligence and emitter geolocation

A sovereign RF intelligence constellation detects, geolocates and characterises radar and communications emitters using TDOA/FDOA techniques, under national tasking authority, with no third-party access to the raw intercepts.

The dependence this ends: Subscribing to foreign RF datasets under licence

The problem with renting someone else's eyes

Every RF intelligence subscription comes with a clause your legal team eventually finds: the licensor may restrict, suspend or terminate access to data over specified regions, at their discretion, for reasons of national policy. That clause is not hypothetical. Commercial and allied-nation RF datasets have been withheld, delayed or geofenced during precisely the crises that made them most valuable. A ministry that cannot task its own sensors, set its own collection priorities or retain raw intercepts in-country is not running an intelligence programme. It is running a dependency.

The post-2022 environment has sharpened this. GNSS jamming across multiple theatres has demonstrated that emitter geolocation is now an operational requirement, not a niche signals-intelligence luxury. Radar systems, communications nodes and electronic warfare assets are radiating constantly. The question is whether your nation captures that radiation on its own terms or reads a summary report produced under someone else's classification rules.

What the physics allows, and where it falls short

Geolocation from space using time-difference of arrival (TDOA) and frequency-difference of arrival (FDOA) requires at minimum two satellites receiving the same emitter simultaneously. Three or more satellites in a well-designed formation reduce position error substantially. The geometry matters enormously: satellites in nearly identical orbital planes produce poor TDOA baselines. Formation design must trade baseline length against the probability that two or more satellites are simultaneously overhead a target area.

Accuracy is honest to state. A two-satellite TDOA fix on a ground emitter, at LEO altitudes of roughly 500 to 600 km, produces circular error probables in the range of several kilometres under good signal conditions. Three-satellite FDOA-augmented fixes, with well-separated baselines and a stable emitter, can approach hundreds of metres. Weak or intermittent emitters, multipath in urban terrain and orbital geometry all degrade that figure. This is useful for cueing other assets and for pattern-of-life analysis. It is not a targeting-grade coordinate without corroboration.

Revisit is a function of constellation size and inclination. A small cluster of three to six satellites in inclined LEO will pass over a mid-latitude area of interest several times per day. Persistent dwell over a single point requires either a much larger constellation or a geostationary component, which introduces its own signal-strength and latency trade-offs. The mission architecture section of this programme defines what revisit is actually achievable at each spending level.

The ambition ladder: constellation to programme

A minimum operational constellation for TDOA/FDOA geolocation is three satellites flying in a coordinated formation, with a ground station capable of downlinking raw or partially processed intercepts and a processing facility inside national borders. Small-satellite missions of broadly this class, drawing on publicly reported national programmes and commercial analogues, have carried budgets in the low tens of millions of dollars for the space and ground segment combined. That buys capability, not capacity: limited simultaneous collection, constrained revisit, a narrow frequency coverage band.

A full sovereign programme adds satellites to the formation, widens frequency coverage across communications and radar bands, adds a second ground station for resilience and redundancy, and builds the in-country processing chain to handle tasking, collection scheduling, signal characterisation and dissemination to cleared analysts. Programme-scale efforts of this kind, comparable in ambition to national SIGINT satellite initiatives documented in open parliamentary and budget records across several mid-sized states, operate on timescales of four to seven years from contract to initial operational capability and involve ongoing operational costs for the life of the constellation.

The honest intermediate step is a pathfinder pair: two satellites, a single ground station, a processing node, and a trained national team that understands what the data can and cannot tell them before committing to the full constellation procurement. Starting there avoids the common failure mode of buying capacity before the analytical tradecraft exists to use it.

What gets built and what you own

The space segment is a formation of 12-16U cubesat platforms carrying RF signal-mapping payloads tuned to the frequency bands of interest, arranged and integrated with a launch vehicle selected for the orbital parameters the geometry analysis specifies. The ground segment is an in-country processing facility, a mission control station and the secure communications links between them. The trained national team is not a courtesy: it is a deliverable, with handover milestones written into the contract.

Source-access terms are agreed before signature. That means the customer receives the satellite software in a form that can be audited, modified and operated without returning to Satellize for permission. Hardware audit rights are included. The formation-flying algorithms, the signal-processing chain and the tasking interface all transfer. What does not transfer is the institutional knowledge accumulated across multiple programmes, which is why the training and handover period is longer than most customers initially budget for. Plan for it.

Limits worth stating before procurement

RF intelligence from LEO is not a replacement for a national SIGINT enterprise with ground-based collection, human intelligence and allied exchange. It is a space-based layer that sees emitters your ground stations cannot reach and provides independent corroboration of what those stations do collect. Conflating the two leads to either over-investment in space at the expense of the broader collection architecture, or disappointment when the satellites do not answer questions they were never designed to answer.

Frequency coverage is a hardware constraint set at manufacture. A payload optimised for VHF and UHF communications bands will not characterise X-band radar emissions. Wideband payloads exist but involve trade-offs in sensitivity and data volume. The mission architecture phase defines band priorities before any hardware is specified, because changing them later is expensive. Similarly, the formation geometry that works well for mid-latitude targets performs differently at high latitudes: inclination is chosen to match the geographic area of interest, not as a default.

What this mission is built from

RF signal-mapping payloads: Primary collection element: intercepts emitter signals across defined frequency bands for TDOA and FDOA processing.
12-16U cubesat platforms: Satellite bus: provides the platform, power, attitude control and downlink for each formation node.
Constellation geometry and revisit design: Determines formation baseline lengths, orbital spacing and the resulting geolocation accuracy and revisit performance.
Inclined low Earth orbits: Orbital regime: inclined LEO is selected to maximise coverage over the latitudes where the areas of interest lie.
In-country data processing: Keeps raw intercepts and geolocation products inside national jurisdiction, under national authority, with no third-party data access.

What you end up owning

The satellite formation, including flight software in auditable source form
In-country ground station and mission control facility
In-country signal processing and geolocation computing infrastructure
Tasking interface and collection scheduling tools, with full source access
Trained national team of satellite operators and signals analysts
All raw intercept data and derived geolocation products, classified under national rules

Handover proceeds in staged milestones: the national team operates alongside Satellize engineers through the first operational year, taking primary responsibility for tasking and collection scheduling before Satellize withdraws from day-to-day operations. Source-access and audit rights are contractually established at signature, not negotiated at handover. Satellize retains no ongoing access to intercept data or processed products after handover is complete; continued support, if required, is a separately scoped arrangement.

Programme parameters

Minimum operational formation	3 satellites (TDOA baseline); 5-6 satellites recommended for FDOA augmentation and redundancy
Satellite class	12-16U cubesat platforms
Orbital regime	Inclined LEO, approximately 500-600 km altitude; inclination matched to area of interest latitude
Geolocation accuracy (indicative)	2-satellite TDOA: several km CEP; 3-satellite FDOA-augmented: hundreds of metres CEP under good signal conditions
Revisit over a mid-latitude area of interest	3-6 satellite formation: multiple passes per day; persistent dwell requires larger constellation
Ground segment	1 primary in-country ground and processing station; second station recommended for resilience
National operator team	Satellite operations, signals analysis and mission control: trained and handed over as programme deliverable
Timeline to initial operational capability	Pathfinder pair: approximately 24-36 months; full constellation programme: 4-7 years
Frequency coverage	Defined at mission architecture phase; VHF/UHF communications and radar bands are common selections; wideband payloads available with sensitivity trade-offs

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 formation geometry assessment.