Memory Alpha


42,471pages on
this wiki
Add New Page
Discuss7 Share


Troi possessed by a Paxan

Troi possessed by a Paxan

Paxan homeworld remastered

The Paxan homeworld

The Paxans were a xenophobic, isolationist, possibly energy-based species inhabiting a planet orbiting a T-Tauri type star in the Ngame Nebula. The Paxans had advanced technology by the standards of 24th century Federation science, which could not counter it. They could manipulate energy structures on many levels and, when communicating with other lifeforms, they could control an individual, as they did with Counselor Troi.

In order to conceal the Paxans' existence from intruders, they terraformed a protoplanet within the system. If an intruder were to come within their territory, they would be confronted with an apparent wormhole, in actual fact, an energy field, which would stun the ship's crew and place them in a state of biochemical stasis. The ship would then be transported out of their space. The intruder would then regain consciousness, assume the wormhole was responsible for their altered position, and depart.

In 2367, the USS Enterprise-D encountered the Paxans on two occasions. On the first occasion, the Paxans' normal attempts to escape detection failed, as Lieutenant Commander Data – an android – was immune to the energy field and was thus able to fend off the Paxan takeover. To escape destruction, Captain Jean-Luc Picard convinced the Paxans to erase the crew's memories of the incident, and ordered Data to never reveal the existence of the Paxans. However, clues left behind by the crew led them to return to the Paxan system, and once again into conflict with the species. Picard was able to convince the Paxans to give them a second chance, this time taking care to erase the clues that had stopped the deception working the first time around. (TNG: "Clues")

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.