Memory Alpha

Ceti Alpha VI

42,437pages on
this wiki
Add New Page
Discuss15 Share
Multiple realities
(covers information from several alternate timelines)
Ceti Alpha VI was the uninhabited sixth planet of the Ceti Alpha system. This system was located in Sector 25712. It was located a considerable distance from the Delphic Expanse and the planet Denobula as well as three days away from Regula I at an unspecified warp speed. The nearest starbase was Starbase 12. (ENT: "Twilight"; TOS: "Space Seed"; Star Trek II: The Wrath of Khan)

The planet exploded for reasons unknown in 2267, approximately six months after Khan Noonien Singh and his followers were exiled on Ceti Alpha V. The shock of the explosion shifted the orbit of Ceti Alpha V, destroying that planet's ecosystem. In 2285, the USS Reliant arrived in the Ceti Alpha system to find a suitable planet for the Genesis Device. Pavel Chekov and Captain Clark Terrell beamed down to Ceti Alpha V, mistakenly thinking it was Ceti Alpha VI. Just before they were captured by Khan and his Augments, Chekov realized that they had made a grave error. (Star Trek II: The Wrath of Khan)

In an alternate timeline, Human refugees fled to the Ceti Alpha system, following the Xindi's successful destruction of Earth in February 2154, during the relentless pursuit of the Xindi to eradicate all Human colonies. (ENT: "Twilight")

Whether the Ceti Alpha system was located in the Mutara sector had not been established in canon.
In Greg Cox' novel To Reign in Hell: The Exile of Khan Noonien Singh, Spock theorizes that a small black hole might have passed through the system, too small to be detected easily by the sensors aboard the Enterprise and that its immense gravity destroyed Ceti Alpha VI and fundamentally alters the orbit of Ceti Alpha V.

External linkEdit

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.