• Welcome! The TrekBBS is the number one place to chat about Star Trek with like-minded fans.
    If you are not already a member then please register an account and join in the discussion!

Revised USS Enterprise numbers

There is no reason to believe that the ship had a registry code, or a name, at all at that point. She simply hadn't been christened at all.

She would HAVE to have the registry, the moment they decided to actually build her. Makes ordering parts a bitch if you don't know where they're going, after all. That's actually part of why the registry scheme exists.
No, you totally missed my point.

You are assuming, I believe INCORRECTLY, that the hull number is the "naval construction contract number." What I'm saying is that NO, it isn't. And that ST-IV is the best on-screen evidence of that.

The ship certainly was built under a contract. But that contract would not have had the number "1701" in it. The contract would be based upon the controlling dockyard facility, and the date that the contract was awarded, and might well have other information as well.

And you're right... it would have to be identified in some fashion the moment that they decided to build her. If you think that's something I'm arguing against... I'm a little insulted. I'm not that stupid. ;)

She was known as something. Just not as the "1701-A."

The thing is, IF the hull code was the "construction contract number," you'd be talking about CHANGING THAT CONTRACT NUMBER after the ship was built, wouldn't you? Which is, of course, utter nonsense.
Naming decisions tend to be political ones, though. So, yes, it could arguably not have had a name until Kirk's incident with the probe, but it's more likely that a name was slated, but was dropped in favor of "Enterprise", again due to political reasons.

The trick is that, until that time, the ship was NCC-1978, and then was updated to NCC-1701-A when the order from Star Fleet came down the pipe. Now, for the 'pounders', this would be a bit annoying, but not a huge deal - just an update to the database. We've already had such things in the US Navy, after all (for technological reasons, mind you, not homage reasons).
Which I'm fine with, except that, again, the ship would not have been formally christened... the "Ti-Ho, 1978" identification would be PLANNED, but not IMPLEMENTED. Yet there would be a unique construction contract in place anyway.

What I'm saying is that this is proof that the code (1701, 1701-A, 1978, whatever) isn't the same thing as the construction contract number. Make sense?
 
You are assuming, I believe INCORRECTLY, that the hull number is the "naval construction contract number." What I'm saying is that NO, it isn't. And that ST-IV is the best on-screen evidence of that.

I'm not assuming that. I'm assuming only that the numbers on each ships are their registry. Since that's a 'canon' statement, going back from TOS itself. What you're forgetting is what the registry is used for.

When a dockworker says "Which ship do I deliver this PB-31 engine too?", the answer is not "THAT ONE", it is the ship's registry. That is exactly why we have registries in the first place. It's not a contract number, it's how the fleet organizes vessels under its control.

So the exact moment fleet says "build twelve destroyers", the Fleet Registrar assigns twelve registries for those destroyers. So long as these registries are unique, whatever they are is totally inconsequential, it's just the way, internally, Fleet refers to the ship, even before formal christening. NCC-1701 could mean "Never Could Count 1701", and it doesn't matter, so long as internally the Fleet says "That ship is NCC-1701, deliver your PB-31 engine to it."

Now, it's very possible that, as a political matter, NCC may really stand for 'Naval Construction Contract' in that it's how the registrar once looked at the numerals - the primary contract number with which everything else is organized. It may no longer really mean that by the time of TOS, even, as Fleet had outgrown the specific use of that prefix, and the relation between the primary appropriations contract and the registry was severed, but it really doesn't matter. So long as the reg ID is unique, that's all Fleet cares about.

So that gets us to changing the registry number. Changing a registry would actually be a big deal internally to the fleet, but not so much to the layman. DD-21, for instance, means little to people not in the Navy, but men in it, particularly those familiar with the ship, know it religiously. Having the DD-21A replace the DD-21 is actually a big deal, and an honor, though most layman would only care about the name.

So, interestingly, the NCC-1701-A isn't the problem, as that actually makes some sense. It's the letters AFTER that that become an issue. The NCC-1701-B wasn't a direct replacement for the NCC-1701-A, after all. They were different classes, did different things, etc. The NCC-1701-E wasn't the same ship type as the NCC-1701-D, either. Granted, at that point, it's now tradition, and the military guards traditions fiercely.

The thing is, IF the hull code was the "construction contract number," you'd be talking about CHANGING THAT CONTRACT NUMBER after the ship was built, wouldn't you? Which is, of course, utter nonsense.

Again, while it would seem silly (and, indeed, is), from a technical standpoint, all that would have to be done is a minor change in the appropriations database to be followed up in the registrar database.
 
Ditto regarding the new Enterprise and the Connies being phased out for the Excelsiors. If the Enterprise was the second ship of the class built as her number might suggest, it was probably the second oldest still out there. I imagine the Enterprise-B (but not 'B' suffix) was already in the works at the time, if not in the early stages of being built. The 'A' was just a political gift and a way for the Federation and Starfleet to politically save face and honor Earth's saviours while the real replacement was being built.

I like to think the 'A' was built from construction spares leftover from the refit program (similar to the way the space shuttle 'Endeavour' was built from spare parts to replace 'Challenger') that was also meant to test the ability to graft Excelsior tech onto the newer Constitutions. This would both explain the way the ship seemed 'put together by monkeys' i.e. in a slapped together fashion, and why it had the newer LCARS-style interfaces and interior designs. I am undecided as to whether or not this ship had a name before it was called the Enterprise-A, but am pretty sure it was 90% done at the time of the Whalesong Crisis.

That's a very interesting and plausible idea. It does explain the otherwise totally unbelievable premise of ST V that the ship was a malfunctioning piece of junk.


Then why were Kirk and the crew so flabbergasted when the existence of another ship named Enterprise was revealed to them?
Okay. They arrived back from TWOK, and were immediately taken to be debriefed for their involvement with the Genesis device and planet. The new Enterprise wouldn't have been in Starbase One - she'd have been in an orbital slip, like the NX-01 and the no-bloody-A,B,C, or D before her and the B, after her. Might not have even had her paint yet, or any systems online to speak of. Morrow isn't mentioning the new ship, because several of the crew are known to have a "thing" about the Enterprise, and they aren't looking for any interference in the project.

No, you're missing the point. Even if all that's true, why wouldn't they have heard about it? The only thing faster than warp drive is gossip. If, as you propose, Starfleet had commissioned a new Connie-class ship with the specific intention from the get-go of naming it Enterprise and replacing the original ship with it, I find it totally implausible that the crew of the original E wouldn't have heard of this happening. After all, TVH is only 3-4 months after TWOK, and it would take much longer than that to build this ship. And Kirk was a member of the admiralty and Spock a prominent captain. There's no way they wouldn't have known about the decision to make a new Enterprise well before the events of TWOK.

So the idea that the E-A was commissioned with the specific intent of replacing the E, without any of the E crew hearing a single word about it, just doesn't make sense.


The events of III play out, and the Bounty returns to Vulcan. They are on Vulcan for an unspecified amount of time. At least a couple of months. Some sources place it at a year and a half.

It was explicitly established in the film as three months. The Okuda Chronology's choice to ignore this and set the film a year or more after TSFS is completely inexplicable.


Note: It's called the Enterprise-Class.

No, not necessarily. The bridge simulator at Starfleet Academy in TSFS -- based on the original refit E's bridge -- has a sign identifying it as "Enterprise Class." But in TUC, Scotty is examining blueprints of the E-A which are labeled "Constitution Class."


Maybe we've just never seen the other ships with contract addendums on canon sources - doesn't prove they don't exist. ;)

I've never seen a cat with antlers. You're correct that that doesn't prove they don't exist. However, it does establish that the probability of their existence is quite low, and that any claim of their existence should be met with extreme skepticism in the absence of hard evidence.

We've seen hundreds of ships in canon. The probability that there would be a significant number of ships with letter suffixes, but that by sheer coincidence none of them ever appeared onscreen except the Enterprises, is unrealistically low.


And ships are never christened until their construction is complete, are they?

Would Kirk, or Scott, have been aware that there was at least one Constitution-type hull under construction? Almost certainly. But that ship simply would not have been named yet...

Thank you. That supports my point. Certainly the commissioning of the ship had to have happened and been known about. But the idea that the decision to name it Enterprise came first -- that the construction contract was treated as an extension of the NCC-1701 contract because someone decided "Let's build a new Enterprise" -- is ludicrous.

This part, I've always had a massive problem with... though it IS in agreement with Roddenberry's interpretation (that "transwarp was a failure").

The thing is, they would not have built a massive and expensive ship around this new propulsion system had it not been previously tested out and proven out in some other venue. In other words... "Transwarp" MUST have worked. Otherwise, the Excelsior would never have been built at all.

Maybe it was like "Force of Nature" -- they found that it had some serious environmental consequences if they continued to use it.

Although I like the interpretation that what was called "transwarp" in ST III was actually the more advanced, faster warp drive of TNG. Once it became established, the "trans-" was dropped and it just became "warp drive," with the term "transwarp" being repurposed to mean "any propulsion system faster than what we currently know as warp drive." (It has to be a blanket term in order to encompass the incompatible types of "transwarp" seen in various TNG & VGR episodes.) Maybe the renaming was for PR purposes to remove the embarrassment of Excelsior's failure -- there was nothing really wrong with its technology, but it gained a bad reputation anyway. (Kind of like how nuclear magnetic resonance machines were renamed magnetic resonance imaging or MRI machines because of irrational paranoia about the word "nuclear.")

We don't actually know exactly how much time passes from the day 1701 returns to Spacedock 'til the day Kirk and Co. board teh 1701-A. And to take it a step further... how long from the time of Khan's attack on the 1701?

Given that NuSpock grows from about age 7 to age 50something or more in a matter of a couple of days, TSFS can't be that long after TWOK, although we can assume that his maturation accelerated at the same rate as the planet's instability. A couple of weeks between films seems reasonable to me, though Vonda McIntyre's novelization of TSFS made it three days.

TVH explicitly begins three months after TSFS, but there's no telling how much time elapsed between the Bounty's return to the 23rd century and the delivery of the verdict at the crew's trial. It could've taken weeks, even months, for the Council to get its act together after the disaster, deal with the business of cleaning up and restoring order to Earth, and then getting around to reviewing evidence and deliberating on the matter of Kirk and his crew. In the film, the spacedock scene seemed to follow immediately on the verdict scene, but it could've been days or weeks later.


So... between the time of TMP and the time of TWOK, how many years passed? Possibly quite a few... and possibly the Enterprise had the crap kicked out of her several times during that period, to the point where her spaceframe was considered compromised, resulting in her being "downgraded" to training duty.

Apparently about a dozen years elapsed. VGR: "Q2" puts the end of the 5-year mission in 2270, so TMP -- at least 2.8 years later -- would be 2273. Now, TWOK, 15 years after "Space Seed," should really be 2282, but again the Okudas' bizarre dating of the movies comes into play; the Okudachron placed it in 2285, and that's been conventional wisdom long enough that it's hard to refute anymore.


I accept it as "Enterprise-class" because, where two contradictory versions are given on-screen, the one that makes the most sense is the one you should accept. Ship classes aren't assigned based upon whether or not two ships look similar... or even whether they're built upon the same hull. No, they're assigned based upon CAPABILITIES.

The idea is that any two ships of a given class are, for all practical purposes, interchangeable. This is the only reason to CARE about "class," after all... you have a job that needs to be done, and you know the capabilities of a certain class of ship, so you send one of the ships of that class to do that job.

That makes sense.

The fact that the Berman-era folks screwed up and gave Scotty a "blueprint" which said "Constitution-class" is something I'm prepared to write off as just another "who cares, they'll take whatever we give them" demonstration by the B&B crew.

Huh? That's a gigantic non sequitur. That blueprint was in TUC, a movie produced by Leonard Nimoy, Ralph Winter, Steven-Charles Jaffe and Marty Hornstein and directed by Nicholas Meyer. Rick Berman was producing TNG on television at the time, but he had no involvement in the movie (beyond calling up Nimoy and asking him to do a guest appearance on TNG to cross-promote the movie). As for Brannon Braga, at the time he was a lowly staff writer in his first year on the show, with only a couple of credits under his belt. He was at the very bottom of a totem pole that had Berman and Michael Piller at the top. He had the smallest possible influence over TNG at the time, and absolutely no influence over TUC. Even if the blueprint had appeared in TNG: "Relics" as you seem to be assuming, it wouldn't have been under Braga's control. There was no "B&B" as a producing entity until 1998, when Braga took over from Jeri Taylor as VGR's showrunner, and no "B&B" as a writing entity until 2000 when they teamed up to co-create ENT and then worked together as a writing team on that show. And the two men went their separate ways after ENT ended in 2005, so there is no longer a "B&B." And there wasn't even a "B" as far as TUC was concerned. Berman only produced the TNG movies, and Braga was only involved with the first two of them as a co-writer.
 
Since that was such a MAJOR plot-point... it's always bugged me that people seem to miss that and assume that somehow "transwarp failed."
Transwarp didn't fail, nor is it apparently the name for a specific propulsion technology, after what we saw on Voyager. It is the name for ANY propulsion technology that TRANScends what is possible with the current WARP technology. They called what they were working with on Excelsior "Transwarp", and probably some version of it ultimately worked well, since (according to some sources) the warp factor multiplier scale was changed from 3rd powers to 5th powers sometime between then and TNG. (Warp 3 TOS = 3x3x3xc, whereas Warp 3 TNG = 3x3x3x3x3xc). But either the Excelsior event convinced them it wasn't ready for prime-time yet, or the Enterprise-Class wasn't built to handle it, or the 1701-A actually did have it - but by the time we saw Kirk and crew aboard her, they had adjusted the warp scale and dropped calling that tech "transwarp".
She would HAVE to have the registry, the moment they decided to actually build her. Makes ordering parts a bitch if you don't know where they're going, after all. That's actually part of why the registry scheme exists.
Yes and yes. :)
The trick is that, until that time, the ship was NCC-1978, and then was updated to NCC-1701-A when the order from Star Fleet came down the pipe. Now, for the 'pounders', this would be a bit annoying, but not a huge deal - just an update to the database. We've already had such things in the US Navy, after all (for technological reasons, mind you, not homage reasons).
I would still contend that it is possible that she was built as 1701-A from the start and was always intended as a replacement for Enterprise - but your way works as well, and I wouldn't argue it strongly one way or the other.
 
No, not necessarily. The bridge simulator at Starfleet Academy in TSFS -- based on the original refit E's bridge -- has a sign identifying it as "Enterprise Class." But in TUC, Scotty is examining blueprints of the E-A which are labeled "Constitution Class."

That's an interesting thought... the NCC-1701 (U) and the NCC-1701-A are actually two distinct starship classes that share the same basic frame. The NCC-1701 (U) is actually an "Enterprise Class" ship, and the NCC-1701-A is "Constitution (U)" class.

If we ignore GR and stick to TVH and TFF's 'canon on-screen' evidence, we know that the NCC-1701-A had a refined transwarp drive, and that the NCC-1701 (U) did not. Even if everything else is the same, that 'little' difference (a dramatically different primary drive type) would be enough to justify the ships being two different classes, and the whole argument is actually moot.

This would assume a timeline of 2245 - USS Constitution built, USS Enterprise built. 2271 - USS Enterprise uprated to Enterprise class. Somewhere around 2285 - USS Constitution uprated to Constitution (U) class. USS Enterprise-A built to Constitution (U) specifics.
 
She would HAVE to have the registry, the moment they decided to actually build her. Makes ordering parts a bitch if you don't know where they're going, after all. That's actually part of why the registry scheme exists.
Not necessarily. My experience is with aircraft production, but I can't imagine that it would be much different for ships (or fictional starships). When you get down to specific aircraft, there are many different ways to refer to it.

For example, on the Super Hornet line, we referred to them as E1, E2, F1, etc. They also have a serial number that you can see near the tail. Out in the fleet, they also have a squadron number assigned (I'm not certain as to what the right term is). And I can assure you there were at least one or two other designators that I'm not remembering. And they were all specific to that aircraft.

Another example is the P-8A Poseidon. We engineers typically refer to the individual aircraft as T1, S1, etc., while their effectivity calls out YP001, YP005, etc., and they also have a line number (2589, 2608, etc.). And I'm sure the Navy will assign them their own number as well, while a commercial 737 (which the P-8 is based on) will have a registry assigned (N665US, etc.).

Note also that for the commercial/private planes, I have seen cases where the registry was changed. Usually that's because it changes countries, but there are also cases where it changes in-country.

My point is, the registry "NCC-1701-A" is most likely not the only designator that that specific hull is known by. It's just the only one really visible to the general public (and us viewers).
 
BJ, your argument falls moot that moment Kirk identified the Republic by her registry, and explicitly so. At that moment, the 'baggage' of the Fleet Registrar comes in, such as its purpose. Starships are not assembly-line pieces, like most aircraft, in which pretty much all production is done in one spot, and registry (such as call numbers) and that stuff comes later.

For a large ship, there has to be a primary method of organization in order to build the thing in the first place. Ship components, class systems, etc, are built in many places, have to conform to different specs, and so on, and all that has to be organized well before assembly begins.

The reason for the DD-21 nomenclature, for instance, isn't so that Janes' Fighting Ships can be nice an organized, it's so that when you look up DD-21, you know what pieces go into her, what her design specs are, and so on, and all of this BEFORE that keel is laid down. Each capital vessel is a major undertaking, orders of mangitude beyond any aircraft in the skies now. And that's not even including the issue of refits, upratings, and modernizations, which make each ship, even ships within the same class, somewhat unique.

The purpose of the registry, as long as there have been such things, is to keep all that information straight. With aircraft, one P-32 is pretty much going to be identical to any other, and all you have to do is look at the overall P-32 spec to get it going. With naval ships, The DD-21 and DD-22 may have significant differences that the registrar keeps straight.
 
BJ, your argument falls moot that moment Kirk identified the Republic by her registry, and explicitly so.
If you actually read what I wrote, I said that wasn't the only number that could refer to that hull. The Republic's hull could have had a serial number or some such while they were building her, and only created its registry when it was commissioned. But since it's unlikely that we'll ever see the intricacies of starship production on screen, we'll never know what really goes on, and we can speculate all we want to fit our own little versions of the Trekverse. Besides, there have been cases where navy ships have changed their hull number. That doesn't mean that every database has to be changed to reflect that, since most would rely on other designators.
 
But we're explicitly talking about a franchise (or part of) that was explicitly modelled on the US Navy of the 1950s for that period of time. There may be other numbers (such as how a car has a VIN and a license plate which both identify it), but the key one, the only one that anyone has really ever been shown to give a rats' ass about, is the registry number emblazoned on the hull.

And whatever NCC means, or whatever you feel about the 'bloody A, B, C, or D', the registry as given serves the same purpose as our current US Navy registry system does. Any further conjecture, and any mention of 'possible other numbers' to serve the same purpose, is nothing more than insertum ad nasuem, and best avoided.

(And yes, as part of the US Navy, if Navy ship has its registry changed, then yes indeed every single database that references that ship also changes. That's part if the USR's operations code. And yes, when researching stuff for Jaynz, I've actually looked up all this crap and have lots of books on the subjects.)
 
No, not necessarily. The bridge simulator at Starfleet Academy in TSFS -- based on the original refit E's bridge -- has a sign identifying it as "Enterprise Class."
The following argues against something I was saying earlier, but I don't care: all things for consideration, right? ;)

It could also be that the simulator was Enterprise Class. There is precedent for this in the real-world current U.S. military - there are simulators for naval vessels that are completely on land, but are built with most of the same parts you'd build a real ship out of. Those simulators have their own "ship" classes and registry numbers, and are mostly built by the same contractors. This really goes to what was mentioned earlier about different classes being about different ship capabilities: 'cause if you think an admiral wouldn't want to send a TOS ship to do a TMP ship's job, just imagine how upset he'd be when he discovered he had ordered a simulator to go do it!
 
(according to some sources) the warp factor multiplier scale was changed from 3rd powers to 5th powers sometime between then and TNG. (Warp 3 TOS = 3x3x3xc, whereas Warp 3 TNG = 3x3x3x3x3xc).

No, actually, in the TNG warp scale as given in the Okuda references, the velocity is roughly the warp factor to the power of 10/3 (3.3333333...) times the speed of light, that is, the cube root of the tenth power. Warp 2 is 10c; 2 to the 10th is 1024, the cube root of which is 10.079. And so on.

Although the "official" warp conversion scales given in the reference books are always way too slow to account for the velocities depicted onscreen.


If we ignore GR and stick to TVH and TFF's 'canon on-screen' evidence, we know that the NCC-1701-A had a refined transwarp drive, and that the NCC-1701 (U) did not.

What canonical evidence is there that 1701-A had a transwarp drive of any kind? Are you basing that on the 1701-A bridge console displays printed in Shane Johnson's Mr. Scott's Guide to the Enterprise? That book is often misinterpreted as "proof" that 1701-A had transwarp, but actually Johnson altered Mike Okuda's graphics to add references to transwarp.


It could also be that the simulator was Enterprise Class. There is precedent for this in the real-world current U.S. military - there are simulators for naval vessels that are completely on land, but are built with most of the same parts you'd build a real ship out of. Those simulators have their own "ship" classes and registry numbers, and are mostly built by the same contractors. This really goes to what was mentioned earlier about different classes being about different ship capabilities: 'cause if you think an admiral wouldn't want to send a TOS ship to do a TMP ship's job, just imagine how upset he'd be when he discovered he had ordered a simulator to go do it!

Heck, maybe it was just the simulator for the "Enterprise class" taught by Admiral Kirk. "Aww, dang it, I have a test in Enterprise class today and I forgot to study!" :D
 
What canonical evidence is there that 1701-A had a transwarp drive of any kind? Are you basing that on the 1701-A bridge console displays printed in Shane Johnson's Mr. Scott's Guide to the Enterprise? That book is often misinterpreted as "proof" that 1701-A had transwarp, but actually Johnson altered Mike Okuda's graphics to add references to transwarp.

True, but a lot of the TVH's version of the Enterprise bridge reused graphics and panels from the Excelsior bridge as well. You never can clearly see any of it on-screen, to be sure, but if I'm expected to accept the NCC-985 as a Constitution class named the USS Eagle as 'canon'...
 
Last edited:
True, but a lot of the TVH's version of the Enterprise bridge reused graphics and panels from the Excelsior bridge as well. You never can clearly see any of it on-screen, to be sure, but if I'm expected to accept the NCC-985 as a Constitution class named the USS Eagle as 'canon'...

Who expects you to accept that? I've never heard of it.

I think it's really obsessive and overliteral to treat set decorations that weren't meant to be closely examined as undeniable canon. I mean, there are lots of things visible onscreen that can't be taken as literal truth, like recycled FX footage and matte paintings, visible wires on Nomad or the Sylvia and Korob creatures, obvious stunt doubles in fight scenes, etc. Sometimes what we see onscreen is just an approximation of what we "should" be seeing. Something like TSFS using Franz Joseph's blueprints to stand in for the movie-era Enterprise interior or the TVH bridge recycling panels from the Excelsior falls into the same makeshift category -- it's not literally meant to be the same thing, it's just an approximation they used to save time and money.

It's a myth among fans that "canon" means "anything and everything ever seen onscreen." Canon is simply the original body of work as a whole, and the creators of a canon often disregard or retcon past elements of it (for instance, "The Alternative Factor"'s explanation of antimatter was disregarded everywhere thereafter, Spock's statement that "one of my ancestors married an Earth female" was revised to make it his father, Trills and Tellarites and other species were redesigned, etc.). A canon is a flexible thing that only pretends to be a uniform whole. It's not something that forces you to adhere slavishly to every tiny detail within it.
 
It's the Okuda-definition of canon, where his encyclopedia is gospel, yadda yadda...

I don't buy the Eagle nor do I really worry about Transwarp needing 'canon' explanations, or Roddeberry's rather inane rantings come that time period. To me, we know that the warp scale changed, we know that Transwarp was put on a huge-ass ship, and the ship worked a couple of years later. To me, Transwarp, as defined in TSFS, worked, and wound up being what TNG simply called 'warp'.
 
I like to think that the Excelsior's transwarp stemmed from the discovery of the 'new warp scale' as seen in the TNG technical manual. It started as a variation of the 'interphase' type drive described in 'Mr. Scott's Guide' - more like the hyperdrive of Star Wars than our regular Star Trek warp drive, with the ship fully exiting and re-entering normal space after a predetermined period.

I'm convinced this was a failure - not because of the engine, which worked fine, but because of the ship's structural integrity being too weak for sustained flights (as seen in - dare I invoke its name?- VGR's 'Threshold.') However, the original drive was converted into an 'ordinary' but incredibly efficient and fast warp drive, and the innovations made in building it led to the modern warp drive layout as seen in chronologically later productions. The term itself would be later be used to describe any type of 'tunneling' warp drive.

All this makes me want to start working on my Excelsior Technical Manual again... I had that and the test-build Enterprise-A in the writeup for that...
 
It's the Okuda-definition of canon, where his encyclopedia is gospel, yadda yadda...

That is a total myth among the fans. The Encyclopedia and Chronology overtly state that their conjectures are merely that, conjectural suggestions that nobody is bound by. Any fans who accuse Okuda of "forcing" them to follow his conjectures are merely betraying their own inability to read carefully. Heck, Mike Okuda posts regularly in this forum -- you can ask him yourself. Or you can just get out the texts and actually read where it says they're just conjecture and are not meant to quash anyone else's creativity.
 
I like to think that the Excelsior's transwarp stemmed from the discovery of the 'new warp scale' as seen in the TNG technical manual. It started as a variation of the 'interphase' type drive described in 'Mr. Scott's Guide' - more like the hyperdrive of Star Wars than our regular Star Trek warp drive, with the ship fully exiting and re-entering normal space after a predetermined period.

I'm convinced this was a failure - not because of the engine, which worked fine, but because of the ship's structural integrity being too weak for sustained flights (as seen in - dare I invoke its name?- VGR's 'Threshold.') However, the original drive was converted into an 'ordinary' but incredibly efficient and fast warp drive, and the innovations made in building it led to the modern warp drive layout as seen in chronologically later productions. The term itself would be later be used to describe any type of 'tunneling' warp drive.

All this makes me want to start working on my Excelsior Technical Manual again... I had that and the test-build Enterprise-A in the writeup for that...

Works for me.
 
If you are not already a member then please register an account and join in the discussion!

Sign up / Register


Back
Top