1,600 km

Sedna is a detached object between the Kuiper belt and the Oort cloud. It is a Dwarf planet. It is also the second reddest object in our Solar System, after Mars. Sedna was discovered in 2003 by scientists searching for Kuiper Belt Objects. They found out that it takes 10,500 years to orbit the Sun.

For most of its orbit it is even farther from the Sun than at present, with its aphelion estimated at 937 astronomical units[3] (31 times Neptune's distance), making it one of the most distant known objects in the Solar System other than long-period comets.[b][c] Sedna's exceptionally long and elongated orbit, taking approximately 11,400 years to complete, and distant point of closest approach to the Sun, at 76 AU, have led to much speculation about its origin. The Minor Planet Center currently places Sedna in the scattered disc, a group of objects sent into highly elongated orbits by the gravitational influence of Neptune. However, this classification has been contested, because Sedna never comes close enough to Neptune to have been scattered by it, leading some astronomers to conclude that it is in fact the first known member of the inner Oort cloud. Others speculate that it might have been tugged into its current orbit by a passing star, perhaps one within the Sun's birth cluster (an open cluster), or even that it was captured from another star system. Another hypothesis suggests that its orbit may be evidence for a large planet beyond the orbit of Neptune. Astronomer Michael E. Brown, co-discoverer of Sedna and the dwarf planets Eris, Haumea, and Makemake, believes it to be the most scientifically important trans-Neptunian object found to date, because understanding its unusual orbit is likely to yield valuable information about the origin and early evolution of the Solar System.[12]

Ad blocker interference detected!

Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.