Why shouldn't we simply rely on the existing Cospas-Sarsat system instead of building our own?

Cospas-Sarsat is excellent baseline infrastructure, but it is governed by a four-nation agreement (US, Russia, Canada, France) and prioritises international interoperability over national operational control. A sovereign constellation lets you set your own alert-routing priorities, integrate with national emergency databases in real time, and avoid the scenario where geopolitical tensions disrupt your access to distress-alert data. You can still interoperate with Cospas-Sarsat as a secondary relay while owning the primary national layer.

What orbit should a community SOS beacon constellation use?

LEO (400–600 km altitude) is the right default: it minimises path loss for low-power beacons, enables sub-90-second latency with sufficient plane coverage, and keeps launch and satellite costs manageable with nanosatellite or microsatellite form factors. MEO adds near-instantaneous global coverage (as Cospas-Sarsat MEOSAR demonstrates) but raises satellite complexity and cost significantly. GEO is inappropriate — the round-trip path loss makes it impractical for the 5-milliwatt transmitters typical of community PLBs.

How many satellites do we actually need for continuous national coverage?

For a mid-sized nation (500,000–2,000,000 km² territory), a store-and-forward constellation of 16–24 LEO nanosatellites in sun-synchronous or high-inclination orbits typically achieves average revisit times under 15 minutes. For near-real-time (< 2 minute) coverage over the full national footprint, 60–80 satellites are needed. Running detailed Systems Tool Kit (STK) coverage analysis against your specific latitude band before procurement is essential.

Can the same constellation handle other applications beyond SOS beacons?

Yes, and this is one of the strongest economic arguments for building rather than buying. The same nanosatellite bus carrying an SOS beacon receiver payload can simultaneously carry AIS receivers for maritime domain awareness, GNSS radio-occultation sensors for atmospheric profiling, and IoT telemetry gateways for flood gauges or seismic sensors. Multi-mission architectures spread launch and operations costs across several government departments, improving the programme's cost-benefit ratio substantially.

What happens to SOS alerts during a solar radio blackout or geomagnetic storm?

Severe geomagnetic storms (Kp ≥ 8) can degrade LEO UHF/VHF links and temporarily disrupt ground-station uplinks. Robust architectures mitigate this through onboard store-and-forward buffers (retaining alerts for up to 6 hours), multiple geographically distributed ground stations, and cross-link relaying where satellites can pass alert packets between each other before downlinking. Space weather hardening should be a procurement requirement, not an afterthought.

How do we prevent the false-alarm problem from overwhelming our national rescue coordination centre?

Three measures are proven to work: mandatory beacon registration linked to a national identity or vessel database (so an RCC can call a registrant before dispatching assets), firmware-enforced activation delays requiring a deliberate multi-step trigger, and annual beacon self-test protocols that flag defective units. Cospas-Sarsat member nations that have implemented national registration databases report false-alarm rates dropping from ~97% to below 70% within three years of rollout.

Is 406 MHz the right frequency, or should we consider alternative bands like UHF IoT or LoRa?

406.0–406.1 MHz is the only internationally protected distress band for satellite-aided search and rescue, and using it ensures interoperability with global RCCs and legal recognition under SOLAS and the ITU Radio Regulations. LoRa and sub-GHz ISM-band IoT technologies can complement beacon systems for community sensor networks and two-way messaging, but they carry no regulatory status as distress signals and must not be positioned as primary SOS infrastructure for life-safety applications.

What does a sovereign SOS beacon programme cost to build and operate?

A credible national constellation of 24 LEO nanosatellites with ground segment, mission control, and beacon registration database typically costs $40–80 million USD to build and $4–8 million per year to operate, depending on domestic industrial capacity. Contrast this with perpetually paying a foreign commercial operator $8–15 per active beacon per year for data relay, which provides no control over routing, no integration with national crisis management systems, and no domestic industrial return. At scale — tens of thousands of registered beacons — sovereign ownership typically breaks even within 7–10 years.

6.7.5Live

Community SOS Beacons

Q: Can the same constellation handle other applications beyond SOS beacons?

Yes, and this is one of the strongest economic arguments for building rather than buying. The same nanosatellite bus carrying an SOS beacon receiver payload can simultaneously carry AIS receivers for maritime domain awareness, GNSS radio-occultation sensors for atmospheric profiling, and IoT telemetry gateways for flood gauges or seismic sensors. Multi-mission architectures spread launch and operations costs across several government departments, improving the programme's cost-benefit ratio substantially.

Q: What happens to SOS alerts during a solar radio blackout or geomagnetic storm?

Severe geomagnetic storms (Kp ≥ 8) can degrade LEO UHF/VHF links and temporarily disrupt ground-station uplinks. Robust architectures mitigate this through onboard store-and-forward buffers (retaining alerts for up to 6 hours), multiple geographically distributed ground stations, and cross-link relaying where satellites can pass alert packets between each other before downlinking. Space weather hardening should be a procurement requirement, not an afterthought.

Q: How do we prevent the false-alarm problem from overwhelming our national rescue coordination centre?

Three measures are proven to work: mandatory beacon registration linked to a national identity or vessel database (so an RCC can call a registrant before dispatching assets), firmware-enforced activation delays requiring a deliberate multi-step trigger, and annual beacon self-test protocols that flag defective units. Cospas-Sarsat member nations that have implemented national registration databases report false-alarm rates dropping from ~97% to below 70% within three years of rollout.

Q: Is 406 MHz the right frequency, or should we consider alternative bands like UHF IoT or LoRa?

406.0–406.1 MHz is the only internationally protected distress band for satellite-aided search and rescue, and using it ensures interoperability with global RCCs and legal recognition under SOLAS and the ITU Radio Regulations. LoRa and sub-GHz ISM-band IoT technologies can complement beacon systems for community sensor networks and two-way messaging, but they carry no regulatory status as distress signals and must not be positioned as primary SOS infrastructure for life-safety applications.

Q: What does a sovereign SOS beacon programme cost to build and operate?

A credible national constellation of 24 LEO nanosatellites with ground segment, mission control, and beacon registration database typically costs $40–80 million USD to build and $4–8 million per year to operate, depending on domestic industrial capacity. Contrast this with perpetually paying a foreign commercial operator $8–15 per active beacon per year for data relay, which provides no control over routing, no integration with national crisis management systems, and no domestic industrial return. At scale — tens of thousands of registered beacons — sovereign ownership typically breaks even within 7–10 years.

Person pressing an orange emergency beacon device outdoors during a flood emergency in a rural village — Flooding isolates distant communities, making satellite SOS beacons a lifeline when roads and signals fail.

How Community SOS Beacons Reach Rescuers

1
Beacon activation
406 MHz distress signal transmitted locally
2
Satellite relay
COSPAS-SARSAT LEO/MEO satellite captures signal
3
Ground processing
LUT decodes GPS location, ID, timestamp
4
Rescue dispatch
SAR coordinator alerts nearest response team

A pressed beacon triggers a 406 MHz signal relayed by satellite to rescue coordinators within minutes, pinpointing survivors precisely.

Page in the build queue

This application has its place in the atlas. The full page — short and long descriptions, what-matters bullets, sovereignty rationale, and the eight-field architecture block — is being written next.

Maturity reading: Operational systems exist with paying customers. Phase 1 built §4.1 (Maritime Intelligence) end-to-end as the depth-and-format reference. Section 4 is the next section to graduate from scaffold to full content; the rest follow on the roadmap.

Related applications

6.7.4 · Previous

Responder Mesh Networks

All in disaster communications

Bring this into your sovereign programme.

All solutions Speak with engineering