Identify the spacecraft and partnership

EgyptSat is an Egyptian Earth-observation program associated with the National Authority for Remote Sensing and Space Sciences, NARSS. Its generations involved different engineering partners: the first spacecraft was built with Ukraine’s Yuzhnoye, while later members involved Russia’s RSC Energia. This history belongs to an imaging program, distinct from Nilesat’s communications services and the later Chinese-Egyptian MisrSat cooperation.

The 2010 operational-experience abstract by M. Argoun describes Egyptian participation in testing, training and technology transfer for the first mission. That is evidence of specified activities; it does not say that every component was designed and manufactured in Egypt. Cooperation can build capability through particular tasks, and the useful question is which tasks people actually performed.

MisrSat 1, also called EgyptSat-1, launched on 17 April 2007. The 2014 EgyptSat-2 appears in this archive as MisrSat-2 — S39678. MisrSat A is EgyptSat-A, launched on 21 February 2019. These names can be cross-checked against international designators 2007-012A, 2014-021A and 2019-008A.

The satellite called MisrSat-2 that launched in 2023 has a different identity, 2023-187B, and belongs to the separate Chinese-Egyptian cooperation course. A name search without the date or identifier can mix those two spacecraft. Likewise, the launch-preparation photograph shows several satellites together; the identifying arrow and caption distinguish EgyptSat-1 from its companions.

Use the identifier as well as the name

WMO’s entries list EgyptSat-1 and the 2014 EgyptSat-2 as inactive, while its EgyptSat-A entry, last updated in February 2026, lists that spacecraft as operational. Those are dated catalogue statements, not a live health feed. The EgyptSat-2 failure chronology is reported differently across sources; this course does not turn conflicting day-level dates into a settled causal account.

A design lifetime, an expected end date, an end of operations and atmospheric reentry describe different things. An object may remain in orbit after it stops providing data. Conversely, a mission may continue beyond an initial design target. When recording a program’s history, attach the source date and the kind of milestone rather than collapsing all of them into a single end date.