Memory Alpha

Minos Korva

42,462pages on
this wiki
Add New Page
Discuss0 Share

Minos Korva was a Federation system located four light years from the Federation-Cardassian border and eleven light years from the McAllister C-5 Nebula.

In the Federation-Cardassian War, the Cardassians attempted to annex Minos Korva.

In 2369, Starfleet believed that the Cardassians would launch an invasion of Minos Korva from the McAllister C-5 Nebula. The invasion was avoided because the USS Enterprise-D, under the command of Captain Edward Jellico, preemptively prevented the invasion by detecting the Cardassian fleet hiding in the nebula. (TNG: "Chain of Command, Part II")

Galen mentioned this incident at Minos Korva when he described William T. Riker's tendency for insubordination to Arctus Baran in 2370. (TNG: "Gambit, Part I")

In the aired "Chain of Command, Part II", Minos Korva was identified as a Federation system, while, in the script and in lines cut from the episode, Minos Korva was identified as being both a star system and a planet with two million colonists. (The Star Trek Encyclopedia (3rd ed., p. 303) identified Minos Korva as a planet.) In lines cut from the episode, it was revealed that after Starfleet Command had arrived at the decision to defend Minos Korva from a Cardassian invasion, the Federation starships USS Berlin, USS Aries and USS Sutherland had been dispatched to Minos Korva's sector. According to the pronunciation guide, Minos Korva was pronounced as "mee-nos KOR-va".
According to the Star Trek: Star Charts (p. 47; "United Federation of Planets I") and the Stellar Cartography: The Starfleet Reference Library ("Federation Historical Highlights, 2161-2385"), the Minos Korva system was located in the Alpha Quadrant. The primary was a M-class star. In 2378, Minos Korva was listed as a Federation member.

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.