FANDOM


110
111-Solomon SCE RichB
Soloman
Vital statistics
Position Engineer
Age Unknown
Status Active 2376
Physical attributes
Height Unknown
Weight Unknown

Soloman (originally 110) was a Bynar in the 24th century. He was bonded with 111 in a single tandem unit. During the Dominion War, 110 and 111 were civilian advisors to Starfleet, and assigned to the Starfleet Corps of Engineers ship USS da Vinci as computer experts.

During a salvage mission aboard "The Beast" in early 2376, the SCE team were attacked by a group of insectoids that had seized control of the vessel. During the attack, 111 was killed in front of 110 and the rest of the team. 110 was so distraught at the loss of his bondmate that he had to be carried back to the da Vinci.

Although distraught for some time other the death of 111, 110 still participated in several missions for the da Vinci. 110 proved himself most vital during a mission to repair the world-computer named Ganitriul. A few days later, he also joined the team that investigated the Omearan Starsearcher known as "Friend". 110 was tasked with trying to interface with "Friend"'s computer, which he successfully succeeded. The link between 110 and Friend was strong, and "Friend" invited 110 to become his new pilot following the death of former pilot, Jaldark Keniria. However, he decided he was better on his own.

Though Bynar custom was for "singletons" such as himself to rebond with another, 110 decided to do so would sully 111's memory. He chose to remain aboard the da Vinci, and after a suggestion made by Captain David Gold, took the name "Soloman" and formally joining Starfleet as an enlisted crewman. (SCE eBook: Hard Crash) This decision subjected him to the prejudice of his fellow Bynars, in particular 1011 and 1110, a unit working on Project Ishtar on Venus.

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.