Memory Alpha

Richard Castillo

42,154pages on
this wiki
Add New Page
Discuss12 Share
Multiple realities
(covers information from several alternate timelines)
"If you get back to Earth, and you see a man, say, in his late fifties, taking a hard, long look across a crowded room... hey, you never know."
– Richard Castillo, 2366 ("Yesterday's Enterprise")

Richard Castillo was a Starfleet lieutenant junior grade serving as helmsman aboard the USS Enterprise-C in 2344.

In that year, the Enterprise-C, under the command of Captain Rachel Garrett, responded to a distress call from the Klingon outpost at Narendra III, which was under attack by four Romulan Warbirds. As the Enterprise-C was defending the outpost, the weapons discharges resulted in the creation of a temporal rift, through which the badly damaged Enterprise-C drifted, arriving in the year 2366. Upon emerging from the rift, the crew encountered their ship's immediate successor, the USS Enterprise-D, whose captain, Jean-Luc Picard, informed them that the Federation was at war with the Klingon Empire, and was on the brink of defeat.

As the crew of the Enterprise-D assisted their counterparts in making repairs, Castillo made the acquaintance of Tasha Yar, the Enterprise-D's chief tactical officer. It was eventually determined that the Enterprise-C's journey through the rift had resulted in the creation of an alternate timeline, and that, if they wished to restore the proper flow if history, the Enterprise-C would have to return through the rift, in the middle of the battle with the Romulans. Although much of the crew was initially skeptical, as returning to the battle with the Romulans would almost certainly result in their deaths, Captain Picard pointed out that, if a Federation starship were to sacrifice itself in defense of a Klingon outpost, such an act would be seen as extremely honorable by the Empire, and would perhaps avert decades of war. Before the Enterprise-C could depart, however, both ships came under attack by a Klingon Bird-of-Prey, resulting in Garrett's death.

As the highest-ranking crewmember left alive, Castillo took command of the Enterprise-C, and prepared to take the ship back through the rift. This caused a certain amount of distress for both Castillo and Yar, who had developed romantic feelings for one another. Eventually, however, Yar decided to join Castillo and the crew of the Enterprise-C when she learned that she had died a meaningless death in the other timeline. Eventually, Castillo led the Enterprise-C back through the rift, repairing the timeline and leaving the crew of the Enterprise-D with no memory of the events which had transpired. (TNG: "Yesterday's Enterprise")

It is unknown if Castillo survived the attack when the Enterprise-C was sent back into the rift, although it is possible he was one of the prisoners who was taken to Romulus as revealed in "Redemption II".
The final draft script of "Yesterday's Enterprise" describes Richard Castillo thus; "Castillo is ruggedly handsome, with jet black hair and fiery eyes." Richard Castillo was played by Christopher McDonald. The costume for Castillo included three five-year service pins, meaning that Castillo had been in Starfleet since at least 2329.



In the Star Trek Online mission "Temporal Ambassador", it is revealed that the Enterprise-D's battle with the Klingons in "Yesterday's Enterprise" caused the Enterprise-C to emerge from the temporal rift in the Azure Nebula in 2409, rather than Narendra III in 2344. The alternate timeline remains in place, and the Federation has fallen to the Klingon Empire (which in turn fell to the Dominion years later). The Enterprise and her crew - including Castillo - are captured by the Tholian Assembly and held aboard a base in the Azure Nebula, where the player must help them escape and reach the temporal rift so they can return to 2344.

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.

Also on Fandom

Random Wiki