Leer esta página en español: ES
Contact

Fit and questions

Mission constraints and answers to what comes up at the first technical meeting.

In scope and out of scope

Illustration A DUT that fits the payload slot.

In scope

  • Space electronics DUT —FPGAs and SoCs, DC-DC and PCDUs, radios, memory, sensors, detector front-ends— with ground qualification done or under way.
  • Fits in 1/3 U or 1U with a power profile compatible with a CubeSat bus: burst testing rather than continuous full-power operation.
  • You need your own dataset of LEO behaviour, publishable and traceable to dates, orbit and environment.
  • A representative LEO environment works for you: the orbit is set by the rideshare, not chosen by contract.
Illustration More than 1U does not fit: whatever sticks out of the slot is marked in red.

Out of scope

  • An operational platform or a constellation service: this is a demonstration mission.
  • More than 1U, propulsion, cryogenics, fine pointing, high continuous power or bulk data download.
  • A date or orbit fixed by contract: the window depends on the launcher manifest.
  • TRL 3–4: ground qualification comes first.
  • A crewed environment, the ISS or hardware recovery.

Questions from the first technical meeting

1U or 3U?−

It depends on your DUT envelope and power draw. The 1U leaves 1/3 U of payload on a 2/3 U bus with body-mounted cells and is the entry format. The 3U leaves 1U on a 2U bus with deployable panels, for whatever does not fit in a third or needs more power.

Both carry a single customer per satellite. Mass, power and data for each format: [PENDING]. Parameter-by-parameter comparison on the platform page.

How long from signature to having the data?+

The overall schedule is [PENDING] and is made up of integration and the environmental campaign, waiting for the rideshare window, LEOP and commissioning, the in-orbit test campaign and final processing.

The part we control least is the launch window: manifest delays are common in the industry and we pass them on as they are, without rescheduling the later phases on our own.

Who owns the data?+

You do. The payload's raw and processed data are wholly owned by the customer, with no usage licence reserved for us. You can publish them, include them in your documentation or hand them to a third party without asking us.

We keep the platform telemetry and the operations logs, which we need to operate the satellite and for our own system learning. We do not publish your name, your component or any result without written authorisation; the confidentiality agreement is mutual and is signed before the technical exchange.

What about ITAR and export control?+

Apollo Orbitals is a Spanish entity and operates under the European Union dual-use regime, Regulation (EU) 2021/821, as well as Spanish regulations on foreign trade in defence and dual-use material.

If your component contains content subject to US ITAR or EAR, the licence is your organisation's responsibility before DDTC or BIS, and includes the retransfer to the launch provider and the operator. We classify the hardware with you at kick-off and structure the mission to minimise transfers, but we do not act as legal advisers. The exporter of record and the launch jurisdiction are set per mission: [PENDING].

What happens if the launch fails?+

Launch risk follows the launch provider's terms, which we pass through to the contract. Re-flight policy and insurance cover: [PENDING].

We recommend keeping a spare FM: with hardware available, a re-flight comes down to integration and the next window.

And if the satellite fails in orbit?+

The contract defines a minimum success criterion —what data volume and what coverage of the test profile make up a completed mission— and the consequences of not reaching it: [PENDING].

The data collected up to the failure is delivered all the same, with an analysis of the anomaly as far as the telemetry allows.

Can you fly several components at once?+

One customer per mission, no exceptions: that is what guarantees the operating profile is designed around your test and that no competitor shares the satellite.

Several parts from the same customer in the same payload slot is feasible and assessed case by case, with the split of power and test time agreed in advance.