Engineering -- Warp Engines?

Consider it dropped from my part - with apologies. The intent of the example was to show that a sinister event might be replaced by a ridiculous one, or vice versa, in order to force a parallel history to superficially comply with our recorded one.

Timo Saloniemi

 

The attack of the Klingon battle cruiser in "Elaan of Troyius" would make more sense as well, if a given warp speed were "lower" inside of a solar system.

 

^ As would the high warp maneuvers to avoid the Romulan plasma weapon in "Balance of Terror" which presumebly, took place inside a solar system since a comet with a tail was featured?

 

Also consider that when Kirk ordered the Enterprise to intercept the suicidal Denevan that was flying into the sun, he ordered the ship to leap to Warp 8. So maybe that would mesh in with this line of discussion.

 

Yep, "Operation: Annihilate" is another example of high warp speeds between the star and the 3rd planet orbit that we observe to be significantly slower, but still FTL speeds (on the order of <5.0c)

More examples would be "Tomorrow Is Yesterday" and "The Voyage Home".

"Doomsday Machine" could qualify since the battle takes place around the 3rd planet orbit.

"The Paradise Syndrome" might also qualify depending on the asteroid's approach.

In "The Voyage Home", the BOP's warp speed appears to be even only sublight when they go to warp in the atmosphere and they probably become FTL at some point past Earth's affect.

"Elaan of Troyius" might also qualify since the Enterprise is heading from the "outer planet" to the "inner planet"... depending on where the inner planet in

"The Balance of Terror" I think alternated between "shallow" and "deep" water FTL since they do fight around a comet with a tail.

"Journey To Babel" interestingly might be out in "deep water" where the Orion ship at Warp 10 was impossible to hit because it really is at a super high FTL speed

Slight tangent - does anyone know when was "subspace" directly associated to "warp drive"?

 

the impression I received was that after the Enterprise entered the system where the Constellation was found, she didn't re-enter warp for the rest of the episode. It was all impulse maneuvering.

The passage of the Enterprise through the comets tail, the duration of the passage, would indicate that at least during that point the ship was sublight, fairly slow sublight at that.

One possibility is that the Romulan ship had to periodically slow to sub-warp speed to rebuild energy reserves or let something "cool off." the Enterprise was conforming to the Romulans movements. Basically the Romulan was making a series of warp dashes. The Romuan commander timed one of these cool off pauses to bring the Enterprise into interaction with the comet, this might have been a old trick on the part of the commander.

Not directly during TOS, although there were indirect references. TNG was more clear with the connection.

<OO>

 

It's possible to have the entire battle sublight although from a TOS POV where a warp driven battle is "normal" as per "Elaan of Troyius" the battle could go like this:

http://www.trekbbs.com/showpost.php?p=4573268&postcount=284

(Also, it wouldn't be impulse maneuvering until after the DDM knocks out the Enterprise's main energizer. At the very least, prior to that the warp engines were being used in a sublight capacity to maintain maneuverability against the DDM.)

Or perhaps not... we don't know the size of the comet's tail which could be more than 1 AU in length and thus huge requiring the Enterprise significant speed to cross it to get to the other side to intercept the Romulan.

That's very possible. The Romulan ship could have been deliberately leading any pursuers to a pre-planned trap.

Curious, I've not found any evidence even indirectly. "Subspace" is usually associated with radio and sensors but never with warp. The closest thing I've seen is the DDM's energy dampening field causing "subspace interference" as a side-effect.

 

I thought the reference was in "The Mark of Gideon", but it turns out it's not.