Folks. The Elysium Star 2 is doing space burial in a SSO orbit. So it is unlikely to have any active components aboard for what is essentially a cargo container.
https://mobile.twitter.com/TSKelso/status/1095609396787331077
And we have an official ID for LACMA ENOCH (#43777) from the SSO-A launch. Only 15 unidentified objects to go…
QuoteSSO-A: DEPLOYMENT STATUSBy Jeff RobertsMARCH 4, 2019[...]we now have confirmation that all expected deployments were successful.[...]https://www.spaceflightindustries.com/2019/03/04/sso-a-deployment-status/
SSO-A: DEPLOYMENT STATUSBy Jeff RobertsMARCH 4, 2019[...]we now have confirmation that all expected deployments were successful.[...]
Nevada Museum of Art has since told Dezeen that currently there is no way of knowing when deployment of the satellite will be approved and whether the satellite will be able to withstand the wait."In spite of the government's being reopen, this still holds true. Unfortunately, that delay impacted us more than we thought it would," Nevada Museum of Art's Amanda Horn told Dezeen.
But nearly four months later, more than a dozen satellites from the launch have yet to be identified in space. We know that they’re up there, and where they are, but it’s unclear which satellites belong to which satellite operator on the ground.They are, truly, unidentified flying objects.The launch, called the SSO-A SmallSat Express, sent those small satellites into orbit for various countries, commercial companies, schools, and research organizations. Currently, all of the satellites are being tracked by the US Air Force’s Space Surveillance Network — an array of telescopes and radars throughout the globe responsible for keeping tabs on as many objects in orbit as possible. Yet 19 of those satellites are still unidentified in the Air Force’s orbital catalog. Many of the satellite operators do not know which of these 19 probes are theirs exactly, and the Air Force can’t figure it out either.
Bit of a necropost here, but this image is HELLA cool:https://twitter.com/DrTen7/status/1154354396576309250
twitter.com/jeff_foust/status/1159241574900879360QuoteJeff Roberts of Spaceflight gives an overview of last year’s SSO-A rideshare mission. Of 64 satellites, 4 cubesats never made contact after deployment; 12 sats never claimed by their owners with Air Force. (And 1 locked in its deployer because of lack of licensing.) #smallsathttps://twitter.com/jeff_foust/status/1159242026627371008QuoteRoberts: very hard to deal with 50+ customers on the same mission, but not against doing another mission like SSO-A. #smallsatSpaceX has a plan that may mean he doesn’t have to worry about that issue again ...
Jeff Roberts of Spaceflight gives an overview of last year’s SSO-A rideshare mission. Of 64 satellites, 4 cubesats never made contact after deployment; 12 sats never claimed by their owners with Air Force. (And 1 locked in its deployer because of lack of licensing.) #smallsat
Roberts: very hard to deal with 50+ customers on the same mission, but not against doing another mission like SSO-A. #smallsat
But 12 were never claimed? What does that mean? Is it voluntary to claim your sats with the Air Force? Or were they abandoned for some reason?
....Also woe to the one guy who didn't get deployed due to some unspecified licensing issue. I mean, they didn't know they had a problem before it was packed up and launched?
To clarify, the 12 cubesats mentioned as "unclaimed" means those organizations did not go to the 18th Space Control Squadron to report which object was their satellite. It does NOT mean those satellites were not functioning or abandoned. -jeff roberts
Quote from: Mandella on 08/08/2019 02:49 am....Also woe to the one guy who didn't get deployed due to some unspecified licensing issue. I mean, they didn't know they had a problem before it was packed up and launched?I don't know any specifics so this is just an educated guess:I'm sure they knew, but the flight was leaving and they were forced to choose: You either get on the flight and hope to get your approval before you get to your destination, or miss the flight entirely and never get a chance.They likely thought their approval was just around the corner.Edit to add: I imagine they had a deadline by which to send their payload to SSO, which was probably quite some time before the launch.
Quote from: mn on 08/08/2019 02:34 pmQuote from: Mandella on 08/08/2019 02:49 am....Also woe to the one guy who didn't get deployed due to some unspecified licensing issue. I mean, they didn't know they had a problem before it was packed up and launched?I don't know any specifics so this is just an educated guess:I'm sure they knew, but the flight was leaving and they were forced to choose: You either get on the flight and hope to get your approval before you get to your destination, or miss the flight entirely and never get a chance.They likely thought their approval was just around the corner.Edit to add: I imagine they had a deadline by which to send their payload to SSO, which was probably quite some time before the launch.The CubeSat concerned was Elysium-Star 2. Not being deployed was likely not a big deal for the customer, as this one was completely passive CubeSat containing only the cremated remains for "space burial".https://space.skyrocket.de/doc_sdat/elysium-star-2.htm
