It looks like you're using an Ad Blocker.
Please white-list or disable AboveTopSecret.com in your ad-blocking tool.
Thank you.
Some features of ATS will be disabled while you continue to use an ad-blocker.
originally posted by: andy06shake
a reply to: eisegesis
Was looking forward to the data this probe will return regarding Pluto, hopefully they manage to sort something out and the mission is still somewhat successful.
The KBOs Hubble found are each about 10 times larger than typical comets, but only about 1-2 percent of the size of Pluto. Unlike asteroids, KBOs have not been heated by the sun and are thought to represent a pristine, well preserved deep-freeze sample of what the outer solar system was like following its birth 4.6 billion years ago. The KBOs found in the Hubble data are thought to be the building blocks of dwarf planets such as Pluto.
originally posted by: oriondc
a reply to: eisegesis
This could be all exactly as they say. But you must admit, the situation is suspicious given the anomalies already detected on Ceres and, from a distance, Pluto. I try to remain grounded in reality but my vote has to be on some sort of censorship here, at some level. It's just too convenient, as another posted said. NH makes it all the way there then sees some crazy stuff then shuts itself off without reason (that we know of)? Like, are you kidding me? That's not even a reasonable Hollywood storyline these days.
originally posted by: Ross 54
Very good news, indeed, from NASA! The problem with New Horizons was quickly traced to a timing error in a command sequence recently sent to the space probe. The problem will be promptly corrected. Science operations are planned to resume on Tues., the 7th. The effect of the interrupted operation on the overall mission is expected to be slight.
Link to article on this situation, below:
thespacewriter.com...
The investigation into the anomaly that caused New Horizons to enter “safe mode” on July 4 has concluded that no hardware or software fault occurred on the spacecraft. The underlying cause of the incident was a hard-to-detect timing flaw in the spacecraft command sequence that occurred during an operation to prepare for the close flyby. No similar operations are planned for the remainder of the Pluto encounter.
We did it ATS, we beat the conspiracy!
originally posted by: LadyGreenEyes
a reply to: eisegesis
So.....we get some pics showing odd dark spots on Pluto, and now, with the probe closer, there is a glitch?
Convenient timing. I get the idea that there are competing forces involved in the space program; some that want to truly explore,a nd some that are determined to prevent some knowledge from reaching the public.
originally posted by: Silcone Synapse
The probe has travelled sucessfully all the 3 billion miles to Pluto and then suffers a "glitch" just as it gets near enough to get proper data and pics?