Tag

Orbiter Sn3

All articles tagged with #orbiter sn3

space2 years ago

SpaceX Launch Results in Loss of Private Spacecraft.

Launcher lost its second spacecraft, Orbiter SN3, after it started spinning uncontrollably following its deployment on a SpaceX rideshare mission. The spacecraft was designed to carry small satellites into their proper orbit after launch but failed to charge its batteries due to its rapid spin. Unfortunately, Orbiter SN3 also carried the payloads of three other customers, causing its primary payload, an on-orbit docking demonstration by space startup Otter Pup, to start spinning as well. Launcher has identified the issue and is ready to make some changes to try again with SN5, which is slated to launch on a SpaceX rideshare mission in February 2024.

space2 years ago

SpaceX Launch Results in Private Space Tug's Uncontrolled Spin

Launcher's Orbiter SN3 space tug, which was designed to deploy smaller satellites into their proper orbits, spun out of control after separating from its SpaceX Falcon 9 launch vehicle due to a software issue. The spacecraft carried the payloads of three customers, but its rotation prevented its solar panels from receiving sunlight to maintain power. Mission operators deployed the customer payloads early to prevent losing the ability to deploy them at all. Launcher lost its first spacecraft, SN1, in February 2023 due to an orientation control issue. The company has begun implementing corrective action to prevent future anomalies.

space2 years ago

SpaceX Launch Results in Private Space Tug's Uncontrolled Spin

Launcher's Orbiter SN3 space tug, which was designed to deploy smaller satellites into their proper orbits, spun out of control after separating from its SpaceX Falcon 9 launch vehicle. The spacecraft carried the payloads of three separate customers, but its rotation prevented its solar panels from receiving the necessary sunlight to maintain power. Mission operators decided to deploy their customer payloads early, rather than risk losing the ability to deploy them at all. The root cause of the anomaly seems to have been a software issue, and Launcher has begun implementing corrective action to ensure this does not occur again on future missions.