AMOS (satellite)
series of Israeli communications satellites

AMOS ("Affordable Modular Optimized Satellite") is a series of Israeli communications satellites operated by Israel-based Spacecom. All AMOS satellites were developed by Israel Aerospace Industries (IAI) using the AMOS bus satellite bus, except for AMOS-5 which was developed by ISS Reshetnev using the Ekspress bus satellite bus, and AMOS-17 which was developed by Boeing on its BSS-702.
Function
The six AMOS satellites used five different launch vehicles: Soyuz, Zenit, Proton, Ariane and Falcon 9; and three different launch sites: Baikonur Cosmodrome in Kazakhstan, Centre Spatial Guyanais in French Guiana, and Cape Canaveral in Florida.
The constellation serves a variety of purposes, including direct-to-home broadcasting, broadband internet access, and communication services for governments and businesses. The satellites are strategically positioned to provide coverage to Europe, the Middle East, Africa, and Asia. The AMOS satellites are built to withstand harsh space environments and have an average lifespan of around 15 years.
Other uses
In addition to its commercial services, the AMOS satellite constellation has also been used for scientific research and military purposes. For example, the AMOS-2 satellite was used to study the effects of space weather on communications systems, while the AMOS-3 satellite has been used to provide secure communication services to the Israeli military.
In addition, it has also been used for military and intelligence operations. The AMOS constellation has also been used for disaster relief efforts, providing emergency communication capabilities in areas affected by natural disasters.
The public source identifies “AMOS (satellite)” as series of Israeli communications satellites. This brief keeps that definition visible, then builds a research path around AMOS, satellite and series.
Why this record matters
A short description can identify a subject without explaining its stakes. For “AMOS (satellite)”, the useful work is to connect “series of Israeli communications satellites” to the records capable of establishing context and consequence.
Vocabulary and entity names are the principal evidence signals here, because they determine the precision of every later search. The source revision retrieved here is dated Sep 2, 2025. The linked authority identifier is Q474206.
The absence of detail may reflect summary conventions rather than a lack of surviving documentation. The lead is largely declarative, so disagreement and counter-evidence require a deliberate search beyond the opening account. Authority statements aid reconciliation but still require their own references, qualifiers and ranks to be checked.
How to read it
Use the entry as an orientation point, then follow its citations and revision history. Names, dates and institutional relationships should be checked against the original record.
- Subject orientation
- Search vocabulary
- Locating named sources
The closest primary source, responsible institution and strongest cited specialist reference.
Three-step research path
- Establish the record: confirm the title “AMOS (satellite)”, its source revision and the description used here.
- Expand the search: follow AMOS (satellite) primary sources, AMOS (satellite) archive and AMOS research across catalogues and specialist indexes.
- Test the account: compare the strongest cited source with the responsible institution’s current record and note any disagreement.
Questions for further research
- Which source most directly establishes the central claim about “AMOS (satellite)”?
- What terminology or title could unlock a more precise catalogue search?
- Which institution is responsible for the underlying evidence?
Search terms from this dossier
This entry incorporates text from “AMOS (satellite)” on English Wikipedia. Contributors are listed in the page history. Text is available under the Creative Commons Attribution-ShareAlike 4.0 License. Selected authority identifiers and statements are retrieved from Wikidata under CC0; their references and qualifiers remain part of the verification path.