Memory Alpha


42,459pages on
this wiki
Add New Page
Discuss13 Share
Starship deploy status 1

Alderaan is listed on a Starship Deploy Status screen, 2365

Alderaan was an inhabited planet. The planet was home to the Alderaan Spaceport.

In 2365, the Federation starships USS Atlantis and NCC-21335 were on diplomatic missions to this planet. It was listed in the chart Starship Deploy Status, which was seen in the Starbase 173 courtroom. (TNG: "The Measure Of A Man", okudagram)

In 2369, the USS Thomas Paine was on a diplomatic mission to this planet. It was listed on the chart Starfleet Operations-Sectors 21538-23079, which was seen in the USS Enterprise-D observation lounge. (TNG: "Chain of Command, Part I", okudagram)

That same year, a transport heading for Deep Space 9 departed from the Alderaan Spaceport. The Bajoran criminal Ibudan was a passenger on this transport. (DS9: "A Man Alone", okudagram)

Expeditions from Sol System, 2123–2190

Original okudagram mentioning Alderaan

The name of this planet originally also appeared in "Up The Long Ladder", on an okudagram on Picard's desk monitor as the destination of HMS New Zealand in 2135. A legible version of the original okudagram appeared in the reference book,
Star Trek: The Next Generation - The Continuing Mission. In the remastered version of the episode, the planet was renamed as Aldebaran. The reference to this planet, as well as the wording of several okudagrams, was an in-joke. Alderaan was, of course, the adopted homeworld of Star Wars' Princess Leia, who claimed to be on a diplomatic mission to Alderaan when captured by Darth Vader in the opening scene of Star Wars Episode IV: A New Hope.
According to the reference book Star Trek Chronology, in the "A" section of the locations index, this planet was listed as "Never visited by the crew of the USS Enterprise-D."

External links Edit

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.