AESP-14: from station cargo to independent satellite

AESP-14 was developed by Brazil’s Instituto Tecnológico de Aeronáutica with support from AEB and INPE. Its route to independent flight used the International Space Station as an intermediate stop. Dragon delivered it to the station on January 12, 2015. The small spacecraft was therefore already traveling around Earth while still being handled as cargo within a much larger inhabited spacecraft.

That distinction matters when reading mission timelines. A transport launch date can identify when the hardware left Earth, while a deployment date identifies when it began operating as a separate object. Neither date by itself establishes that an instrument returned useful measurements. A complete account follows the transitions and asks what each record actually demonstrates, instead of treating every use of the word launch as the same event.

JAXA records that AESP-14 was placed in Kibo’s airlock on January 29. The airlock was depressurized on February 4, and the spacecraft was deployed on February 5 under command from the flight-control team at Tsukuba. The JEM Small Satellite Orbital Deployer provided the interface — open definition between the stored CubeSat — open definition and its release into the external environment. The station supplied handling and deployment infrastructure rather than becoming part of the satellite afterward.

Consider a fictional mission checklist with four entries: delivered to station, installed in deployer, released, and first valid telemetry — open definition received. A photograph of separation can support the third entry while leaving the fourth unresolved. A radio packet can support a later communications milestone if its origin and content are verified. It is useful to celebrate each step without allowing evidence for one step to stand in for all the others.

Separate the mission milestones

Commissioning — open definition checks whether the separated spacecraft is ready for its intended work. Operators may examine power state, temperatures, timing and communications before enabling more demanding activities. In a fictional case with no received signal, several explanations could remain: the transmitter, antenna, power supply, tracking prediction or receiving station might need investigation. Silence alone does not uniquely identify the failed component or prove that no part of the spacecraft is functioning.

The AESP-14 archive entry and JAXA deployment report let you reconstruct the transport and release history. The contemporary report speaks prospectively about Brazilian operations; it is not a later performance review. Keep that boundary when discussing the mission. Development and deployment can provide valuable training while operational objectives require their own evidence. This habit also helps compare student spacecraft with much larger missions that pass through similar readiness gates.