The SS Valiant was not launched in 2065, because Kirk clearly says that it was launched more then 200 years ago, which would be between 2064 to 2040. the exact line from Kirk's first log is "The call letters of a vessel which has been missing for over 2 centuries" --TOSrules 19:10, 31 Aug 2005 (UTC)

Who decided that 2040 would be when "over 2 centuries" ends?
I think you meant to say "The SS Valiant might not have been launched in 2065"
If the Valiant was mentioned with warp drive or any FTL propulsion, it would have to be after April 2063, when mankind discovered FTL propulsion, but before 2065. I still think it could have been within 2065, however -- for example "200 years and two months ago" would still fall under "over 2 centuries" ago. -- Captain Mike K. Barteltalk 22:39, 31 Aug 2005 (UTC)

The episode never says anything about warp drive on the Valiant, although impulse is brought up when talking about getting out of the storm. When you say over 2 centuries, as Kirk did twice you are not talking about 2 centuries 6 months, the time is so insignificant. The rule of thumb is "over 200 years" or "more then 200 years", means between 201 to 225 years ago. Probably not the extreme on either end, more likely in the middle.

As for warp drive it was theorized that the Valiant had it because she was so close to the barrier, but even Kirk notes the ship was not suppose to be there. This ship was not only pushed off course far from the barrier but a half light year past it. That storm had to push the ship way beyond the speed of light, probably faster then the Enterprise. In short, there is no way a ship of even 2065 could ever make it to the barrier, so any theory of warp drive on this ship is unfounded speculation to explain away a problem, and failing. --TOSrules 03:02, 1 Sep 2005 (UTC)

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.