Alsat-3: evaluate a new generation with the right evidence

ALSAT-3A and ALSAT-3B launched in January 2026, extending Algeria’s Earth-observation program through cooperation with China. ASAL’s February overview identifies the pair and describes high-resolution imagery and risk-management applications. These are important program facts, but the overview is not a complete technical acceptance report. It does not publish every calibration — open definition result or demonstrate that every proposed application has already met its requirements.

The new pair follows earlier Alsat generations with different industrial partnerships and development histories. The shared national naming does not make their instruments, operating procedures or image products interchangeable. A user comparing observations across generations should ask how the measurements were made, what corrections were applied and whether differences between sensors could imitate changes on the ground.

Consider an invented emergency-mapping requirement: at least 90 of 100 designated test locations must be placed within ten metres of independently surveyed references. Suppose a trial places 93 within that limit. It passes the stated positional criterion for this test set. That result says nothing by itself about cloud coverage, delivery time, brightness calibration or whether the map correctly classifies flooded ground.

A practical acceptance plan would therefore separate criteria rather than hiding them inside a single success label. It could check location accuracy, observation freshness, processing delay, completeness and the interpretation task. A product might satisfy the positional requirement while arriving too late for a particular decision. Conversely, rapid delivery does not make an inaccurately located feature safe to treat as precise.

Keep acceptance criteria separate

For a recent mission, source dates are especially important. A launch announcement establishes an early milestone; a later commissioning report may add evidence about instruments; a user validation — open definition report can test a particular product. If only the earlier source is available, the reader should preserve that boundary. It is better to describe an intended role accurately than to invent a numerical performance claim or an operational milestone.

Alsat-3 brings the course’s ideas together. Local capability requires demonstrated engineering work, images require calibration, technology demonstrations have limits and services need acceptance tests. Those principles remain useful even when hardware and partnerships change. Follow the archive cards to distinguish the two physical satellites, then use dated primary reports to evaluate which parts of the broader program have been established. A new generation earns a careful explanation of its own rather than a copied description of its predecessor.