|
<< Previous Episode - Season One Index - Next Episode >>
Enterprise Episode Guide - Season One Episode: 26
Shockwave, Part I
 |
| Mission Date: February 2152 |
 |
 |
Ten months into their journey, the crew of Enterprise got a taste of just how devastating temporal violations can be. Just as an away team was about to visit a deep-space colony of a race called the Paraagans, a massive shockwave scorched the planet, wiping out the entire colony. Though Enterprise followed all the appropriate protocols, it appeared that the ship was responsible for the accident. Admiral Forrest convened an emergency meeting of the Command Counsel and came back with a devastating ruling: the mission was cancelled, and Enterprise was to return home, while a Vulcan ship would come and pick up Sub-commander T'Pol and Dr. Phlox.
Later that night, Archer went to bed, and upon turning on the light again, found himself in his San Francisco apartment ... ten months ago. Archer was confused, then heard a familiar voice: Daniels, the time-traveling operative who was supposedly killed months ago by Silik. Daniels explained that the Paraagan colony explosion wasn't supposed to happen, and it was most likely caused by someone who doesn't want Archer's mission to succeed.
Archer woke up on Enterprise, invigorated by these new revelations. Using information gleaned from Daniels, Archer was able to determine that Enterprise was not responsible for the explosion — it was the Suliban. The crew tracked down a Suliban stealth cruiser, and retrieved three data discs, which confirmed Enterprise's innocence. Later, the ship was hailed by Silik, who surrounded Enterprise with cloaked Suliban ships. He demanded Archer's surrender, and threatened to destroy Enterprise. Archer put T'Pol in command of the ship, and headed off ... but when he entered the turbolift, he was suddenly no longer on Enterprise. Instead, he found himself in a ruined alien building, gazing out into a devastated city. Daniels was there, and informed Archer that he was instructed to bring Archer to the 31st century. Apparently, the timeline had been contaminated ... and Daniels had no way of sending Archer back.
Episode info from: www.startrek.com
|