Starship Fleet

Written:  02/02/16
Revised:  02/09/08

It appears as though our junior adjutant has been reading too many holonovels, and the drama’s gone to his head.  Let’s dissect this piece-by-piece and point out the facts.


The Federation cultists believe their Federation has impressive industrial capacity, but they are clearly not familiar with our industrial capacity. We have constructed 25,000 Star Destroyers in the last 20 years and two Death Stars within the last 5 years. These forces, impressive as they are, are still dwarfed in numbers by the massive fleets of dreadnoughts, frigates, escort cruisers, light cruisers, etc. that have been patrolling the galaxy for millennia.

25,000 Star Destroyers.  Considered to be top-of-the-line war ships, and manned by the best the Imperial Navy had, and yet of the ±25,000 constructed, only approximately 200 remain in service with the piteous remnants of the once-dreaded Imperial Navy’s starfleet.  This means that a pack of poorly-armed terrorists were able to destroy and steal a whopping 99.2% of their “best” ships.  With their “great” crews.  As for constructing 25,000 of them, with the large area that the Empire once commanded, if they did any less, they’d look even more foolish than they do now.  With that much space on hand, one should have 25,000 construction facilities, so it is still not an impressive feat, and most facilities should be able to work on multiple projects, simultaneously.  Now, with the Death Star class battlestations, that’s a different story.  They were a pair of hastily-constructed, materially wasteful, heavily-flawed, over-priced military blunders that probably hold records in many different universes.  More than likely, a lot of the construction techniques that were utilized in the construction of such structures as the outdated Hosk Station and the torpedo spheres were utilized in the Death Stars.  This means large, primitive industrial replicators creating massive assemblies in many places, and having them flown in via Hyperspace to assembly plants.

Some Federation cultists make ludicrous claims about us having only a few thousand ships (like their puny Federation), because Han Solo stated in ANH that the Empire couldn't possibly have destroyed Alderaan. He said: "The entire starfleet couldn't destroy the planet. It would take a thousand ships with more firepower than I've-" before being cut off by a hurtling TIE fighter. Frankly, it doesn't take a genius to see that this quote can be interpreted in many ways, not least of which is the fact that Han Solo is demonstrably wrong about the capabilities of the Empire since he claims that it is "impossible" for them to have done what they just did: destroy a planet. For them to twist this quote to claim that the Empire can control millions of star systems with a few thousand ships is typically illogical- he is speaking in the heat of the moment, he obviously knows nothing about the true capabilities of the Empire since he thinks they can't destroy a planet (even though they just did) and the Death Star was too large to possibly be an Imperial space station (even though it was). Furthermore, the density of ships filling the Coruscant sky in TPM indicates that millions of ships travel in and out of Coruscant on a daily basis. This isn't even the full military force of the Empire- it is just the food and supply ship traffic for Coruscant's population! We must repeat, and emphasize that any Federation cultist who makes ludicrous claims about our starship fleets being as small as their puny starship fleets is obviously ignorant, self-delusional, or both.

 Apparently, reading comprehension wasn’t a necessary requirement for recruitment into Imperial Intelligence.  Especially in the little closet the tertiary junior adjutant works out of.  Section 31 surveillance footage actually has the criminal Han Solo saying:

“No…the entire Imperial fleet couldn’t have done this.  It would take a thousand ships massing a lot more firepower than has ever existed.”

-Star Wars, the Star Wars Trilogy, “A New Hope”, Chapter 8, pg.:  103.  Written by George Lucas.

This may go against the statement made days later by General Dodonna:

“The station,” Dodonna went on, “is heavily shielded and mounts more firepower than half the Imperial fleet.”

-Star Wars, the Star Wars Trilogy, “A New Hope”, Chapter 11, pg.:  147.  Written by George Lucas.

I don’t know what the tertiary junior adjutant’s reading, but Dodonna’s statement actually doesn’t contradict Han Solo’s.  Also, let’s not forget that Han Solo, before being a freelance criminal was a military criminal:  an officer in the Imperial Navy.  However, it should also be remembered that generals utilize specialists and junior officer advisors, all the time.  If the tertiary junior adjutant knew anything about the military, he’d know that.  What was Han Solo’s job in the Navy?  What is Dodonna’s military background?  Section 31 has personnel files on both Han Solo and Jan Dodonna.  

Gray-bearded and grizzled, Dodonna appears to be and Academy professor, yet he is one of the most brilliant military tacticians in the galaxy.  He was one of the first Star Destroyer captains in the days of the Old Republic.  He and his best friend, Adar Tallon, were infamous for their knowledge and execution of interstellar battle tactics; Tallon was proficient in ship-to-ship combat, while Dodonna specialized in logistics and siege aspects of war.

-Star Wars, the Essential Guide to Characters, General Jan Dodonna, pgs.:  45-46.  Written by Andy Mangels.

There’s more, though:

Although he didn’t receive medals like those given to Skywalker and the heroic smuggler, Han Solo, Dodonna watched the victory ceremony from the main stage.  He stood proudly as the amassed troops of the Rebellion cheered.  He knew that many of them cheered for him, as well. 

Over the following year, as the Alliance searched for a new base, Dodonna commanded the defense of Yavin Four.  When he received news of Darth Vader’s new Super Star Destroyer, Executor, Dodonna knew that the base would be it’s first target.  One of the Alliance members on the mission to help destroy the Executor was Dodonna’s own son, Vrad.  The rest of the fleet was destroyed, but Vrad managed to escape in a Rebel scoutcraft.

Back on Yavin, as an evacuation to the icy planet of Hoth was imminent, Dodonna received the distressing news that his son was dead.  But then Vrad showed up, his fighter badly damaged.  He and Luke volunteered for what was though to be a suicide mission.  They were going to attack the Executor with a fighter and a power gem that would disrupt the Destroyer’s energy shields.

Although Vrad cracked under the pressure, dumping Luke on an asteroid and planning to escape from the Rebellion and the Empire, his ship was fired upon by the Executor.  Realizing he could never escape, Vrad made a suicide run on the Destroyer, causing minimal damage.  When Luke returned to Yavin Four, he did not tell the general about his son’s cowardice.  It was bad enough that the general had lost his son.

-Star Wars, the Essential Guide to Characters, General Jan Dodonna, pgs.:  45-46.  Written by Andy Mangels.

Han was a talented swoop and speeder pilot by the time he entered the Imperial Space Academy.  There he made friends with the older Mako Spince, and “Trooper” Badure.  Han soon earned the nickname “Slick,” due to a particular slick maneuver he performed in a malfunctioning U-33 loadlifter during class exercises.

Mako and Han became the best of friends, breaking rules and engaging in horseplay and practical jokes.  Spince went too far when he used a gram of antimatter from the physics lab to blow up the Academy’s “mascot moon.”  He was expelled two years before Han Solo graduated.

Han did graduate, with honors, and accepted a commission in the Imperial Starfleet.  He might have had a brilliant career in the Imperial Navy, if not for an encounter with a large, hairy Wookie.

-Star Wars, the Essential Guide to Characters, Han Solo, pgs.:  144-148.  Written by Andy Mangels.

Then, let’s not forget:

Han accepted a general’s commission from Mon Mothma and her Advisory Council.

-Star Wars, the Essential Guide to Characters, Han Solo, pgs.:  144-148.  Written by Andy Mangels.

So, in spite of the tertiary junior adjutant’s desperate attempts to paint Han Solo as an unqualified incompetent on the matter of Imperial Starfleet firepower, a discerning person can plainly see that, in fact, General Han Solo could’ve been just as qualified as Jan Dodonna, if not a little more so.  Dodonna wasn’t even a starship tactics expert, and while some intimate knowledge of starship capabilities was necessary as a siege expert and a starship captain, it was actually his friend Adar Tallon that was the true expert in starship combat.  Han Solo did not lose his commission due to incompetence, but due to compassion (before losing all self-respect and officer’s bearing, and becoming a ruthless murderer and drug dealing smuggler in the employ of a crime lord).  The two mens’ statements do not contradict.

Han Solo:  “…No…the entire Imperial fleet couldn’t have done this.  It would take a thousand ships massing a lot more firepower than has ever existed.”

-Star Wars, the Star Wars Trilogy, “A New Hope”, Chapter 8, pg.:  103.  Written by George Lucas.

Jan Dodonna:  “The station,” Dodonna went on, “is heavily shielded and mounts more firepower than half the Imperial fleet.”

-Star Wars, the Star Wars Trilogy, “A New Hope”, Chapter 11, pg.:  147.  Written by George Lucas.

General Solo (ret.) said that “…the entire Imperial fleet…” didn’t have the firepower to do what the Death Star did.  General Dodonna (ret.) said that the station “…mounts more firepower than half the Imperial fleet.  Both statements are true. If it has more firepower than “…the entire Imperial fleet…”, then that also means that it mounts more firepower than “…than half the Imperial fleet.  Turbolaser yields have already been discussed elsewhere in this document (see:  TurbolaserYieldAndBlastArea).  That volume and magnitude of firepower could very quickly and easily devastate a planet, but reducing it to asteroids like the Death Star could and did; that’s a horse of a different color.

“…massive fleets of dreadnoughts, frigates, escort cruisers, light cruisers, etc. that have been patrolling the galaxy for millennia.”  Again, if you’ve enough production facilities, it isn’t a wonder that there should be a large preponderance of starships.  However, unlike Starfleet, Imperial/New Republic astronautics technologies do not seem to readily advance, which probably necessitates extending the service lifetimes of many of their starship types out way beyond what is best for the design.  Starfleet, while having been around for just a few centuries, does not employ any starships that are a few centuries old; technology progresses far too quickly, and things become outdated, fast.  Very few 23rd century starships are still in service with Starfleet, including the Excelsior- , Miranda- and Oberth-classes, for instance.  The vast majority of the old Imperial fleet, and a considerable percentage of the New Republic fleets, are composed of old, out-dated starships.

Furthermore, the density of ships filling the Coruscant sky in TPM indicates that millions of ships travel in and out of Coruscant on a daily basis. This isn't even the full military force of the Empire- it is just the food and supply ship traffic for Coruscant's population! We must repeat, and emphasize that any Federation cultist who makes ludicrous claims about our starship fleets being as small as their puny starship fleets is obviously ignorant, self-delusional, or both.

  “…obviously ignorant, self-delusional…”.  That’s precisely how I’d profile the Imperial intelligence agent that wrote this report.  Our teams that have done lightspeed breakaway time travel in the star system containing Coruscant (capital and indispensable hub of the Galactic Republic, Galactic Empire and New Republic) have brought back footage of the skies over and around the Senate Building/Imperial Palace/Presidential Palace, and, while the density of traffic is high, there is nothing to indicate what types of ships they actually are, passing overhead.  Due to the multi-layered nature of the world-city of Coruscant, it has an unnaturally, uncomfortably high population, and, chances are, most of the citizens living at or near the surface can afford cars.  There’s also a big probability that the government provides public transportation for it’s citizenry that can or can’t afford it.  The skies of Coruscant did contain air vehicles, as well as starships, but, there is nothing to indicate millions of starships passing through daily.  Nothing.  Anyone saying otherwise is participating in speculation that goes far beyond the ludicrous to the laughable.  There is nothing, even, to indicate that this traffic was all over the world; perhaps the density of traffic seen was only in Imperial City, and less in other regions.

In the first minute of TPM we see that the Trade Federation blockade consists of 2 mile wide starships in geosynchronous orbit, less than 10 miles apart. Since the TradeFed blockade was a full planetary blockade, this means that they had thousands of these vessels in orbit. This isn't even the government- it is a mere shipping company! Furthermore, the blockade itself is described as "trivial" by Qui-Gon; clearly, this was not a stunning quantity of starships to him. Obviously, attempts to equate Imperial fleet size to Federation fleet size are misguided and futile.

Apparently, their intel is very faulty, as is their grasp of history.  Starfleet Intelligence agents and Section 31 operatives utilizing time travel have been able to access the primitive computers located in the Jedi Temple of Coruscant and get transcripts from many of their proceedings.  The late Jedi Master Qui-Gon Jinn did not, in fact, describe the blockade as being ‘trivial’ in making any reference to it’s scope.  What he did say, in fact, was:

“I sense an unusual amount of maneuvering for something as trivial as this trade dispute.  I sense fear, as well.”

-Qui-Gon Jinn, Episode 1:  Star Wars, the Phantom Menace, by Terry Brooks; based on the screenplay and story by George Lucas.  Page:  32.

It sounds as though the writer of this report is trying to convince himself of something.  Also, he is trying to convey more dysinformation by saying the civilization calling itself the Trade Federation was naught more than a company or corporation; that is about as stupid as saying the Ferengi Alliance is a mere L.L.C.  Also, I don’t think most holding companies have viceroys.

                        Additionally, the tertiary junior adjutant is lying (again) about the Trade Federation being “…a mere shipping company! ”.  ‘Shipping companies’ don’t fall under the following description:

The Trade Federation:  In a never ending effort to increase it’s wealth and power, the Trade Federation uses battleships and droid armies to protect it’s profitable trade routes.  Preferring to exploit outlying areas, away from the Republic’s gaze, the Federation has recently targeted the planet Naboo.  While it is illegal to invade a planet or challenge it’s sovereignty, the Federation has decided to escalate it’s blockade of Naboo, forcing it under the Federation’s military rule.  Was this shocking invasion an isolated incident or the first of more to come?  Will other defenseless planets now fall victim to the Trade Federation’s military tactics?

                        -Star Wars Episode 1:  “The Phantom Menace” Scrapbook, the Ultimate Insider’s Guide to the Movie, The Trade Federation, pg.:  20.  Written by Ryder Windham.

                                Another thing to look at is that if it was, in fact “…a mere shipping company ”, the government of the Galactic Republic was absolutely pathetic.  Any so-called interstellar government that is influenced by a shipping company needs to be replaced.  Also, “…a mere shipping company ” would not have any assets that could do anything significant for any real military force (which the Galactic Republic was sorely lacking in, anyway, prior to the raising of the Republic Clone Army by the soon-to-be-emperor Palpatine).

Tarkin smiled at this answer.  “Then I may have useful news for you,” he said.  “I’ve just come from a secret meeting.  Chancellor Palpatine has finally forced a stand-down over the Naboo incident.  The Trade Federation security forces will soon be disbanded.  In the next few months, they are to be assimilated into Republic forces and placed at the disposal of the senate.  All will comply -- even Outland Mining -- or face a centralized and much more powerful military response.”  

Sienar tipped his head to one side.  He had already caught wind of Chancellor Palpatine’s decree.  “The Trade Federation had large reserves of money, and granted, they gave me many more interesting contracts than the Republic did, but I’ve kept my friends in the senate.  I will miss Trade Federation patronage, but I don’t see a complete collapse of Trade Federation influence for some time.  As far as the Republic is concerned…their specifications are neither inspired nor inspiring.  And when I do take a Republic contract, I’m forced to work with aging engineers the senators trust.  I hope that changes.”

  -Star Wars:  Rogue Planet”, Chapter 2, pg.:  34.  Written by Greg Bear.

A common fallacy is the belief that Star Destroyers are exceptionally large even by the standards of the Galactic Empire, when in fact they are unremarkable vessels. The Invincible-class dreadnoughts which patrolled space generations before the first Imperator-class Star Destroyers were commissioned were over 2km long, like the one that Han Solo encountered when he traveled to the Stars' End prison facility.

  Further evidence of how this civilization is slow to bring in new technologies and starship classes.  Many Invincible-class starships, for example, are still in service in the Corporate Sector, and are completely ineffective against newer starships.  When the Yuuzhan Vong vessels arrive, we predict that all that do not immediately retreat will be destroyed in maybe 2 minutes of fighting.  However, the Invincible and Imperator classes of starships are not any longer considered starship engineering marvels, in light of such accomplishments as the Death Stars, torpedo spheres and the Super-class star destroyers (which also includes the Sovereign and Eclipse subclasses).

However, a lone ISD is still an impressive sight for primitive cultures, who are generally incapable of constructing a vessel on that scale (the Federation has never been able to build a starship longer than 700 meters).

Part of the reason the Galactic Empire was such a failure as both a government and a military unit was the fact of it’s great and laughable overconfidence in the face of all odds, great and small.  Ruled by a man that has been profiled as suffering from a great many psychoses, including megalomania and paranoid psychosis, he filled many key cabinet positions with people of like mind.  This allowed the Alliance to Restore the Republic, a shabby pack of militants, to wrest power from him and his servants in far less time than it took to acquire.  Holding a majority share of their galaxy for approximately 2 decades, they lost the vast majority of that galaxy in less than 5 years.  This is the same mentality that allowed a large number of conventional and SOF (Special Operations Forces) troops to be captured and/or killed by a primitive, weak race called the Ewoks of planet Endor.  Because the Empire had never seen massive starships, their overconfidence cost them a key battle, which, in turn, cost them the war and their galaxy.  Even the small holdings they still retain are economically poor and militarily ineffective.  Starfleet has no starships the size of star destroyers, simply because there is no need for them, at this time, and there will be no need for them anytime in the immediate future.  As for star destroyers inspiring awe and dread in cultures that are not technologically advanced enough to design & construct them, themselves, that’s no different than cultures that aren’t far enough along, technologically, to have directed-energy weapons like phasers getting a front-row seat of how effective they are in combat, when all they can respond with is a spear or maybe a projectile weapon.  And I’ve seen that not everyone will back down to a phaser, clearly superior firepower, or not. 

Its length is approximately 1600 meters, and its volume is approximately 9E7 m³. Contrast this with the Federation's front-line warship, the military-version GCS. Several hundred of these ships were deployed in their recent Dominion War, making them the apparent backbone of their fleet (their Defiant-class and Sovereign-class ships are few in number).  The GCS is a mere 650 meters in length, and a mere 6.5E6 m³ in volume. Federation cultists invariably compare the length of the two ships when comparing their size, but volume defines mass, and the volume of an ISD is fourteen times as large as the volume of a GCS. A one-dimensional comparison of length is over simplistic and unrealistic- a 10m sphere is 8 times larger than a 5m sphere, even though it is only twice as wide.

One thing even most intelligent children know is that size doesn’t matter.  While it is true that an Imperial II class star destroyer has a higher volume available to it than, say, an old Galaxy-class explorer, this does nothing to offset the qualitative and technological superiority of the old Galaxy-class.  In the 20th century, while the United States did not have the manpower that the old, former Union of Soviet Socialist Republics did, it’s technological and qualitative superiority more than overcompensated for this gap.  Furthermore, the writer’s over-simplistic graspings as to trying to figure out how many Galaxy class explorers exist are fruitless; there are no published numbers, and nothing to indicate that the Galaxy-class is a ‘backbone’ capital starship.  In battles, while they were numerous enough to be deployed in wings (“wing” 2+ squadrons in naval terminology that are not carrier-based), there is no estimate given (publicly) as to how many actually participated, and if they even outnumbered the revised Excelsior-class.  Likewise, there is no indication as to when the Sovereign-class came into service, and how many currently are in service.  It isn’t even publicized at which point Enterprise was commissioned into the line; it could’ve been the 2nd, it could’ve been the 200th.  Threat forces have no way of knowing, constantly and completely confounded by Starfleet Intelligence and Section 31 counterintelligence programs.  The Defiant-class, however, is clearly numerous, and in many battles with Dominion forces, large elements of them are clearly visible in high profile movements. 

Therefore, even if we disregard the rest of the fleet and exclusively discuss ISD's, the Empire's ISD fleet is as massive as 350,000 GCS's.

I believe the issue of qualitative superiority has already been addressed. Let’s look more in-depth, however, at the telling, stark differences between Imperial/New Republic/Corporate Sector Authority starship design, versus those common to the United Federation of Planets Starfleet.  Then, let’s not forget the fact that star destroyers probably have few (or even no) construction materials in common with the Galaxy-class starship, meaning the mass of the GCS cannot be estimated by guessing at a star destroyer’s mass.

Lack of technological sophistication - It is quite obvious that Imperial/New Republic/Corporate Sector Authority starship design is nowhere near the level of technological sophistication typical of UFP Starfleet designs. Imperial Starfleet starships, for instance, have very limited sensory capabilities. Most of their functions seem very narrow and limited; they are incapable of multiple functions. The Intrepid-class, for instance, while based in part on the previous Galaxy-class, underwent a very large amount of in-progress design changes, as seen below:

“Design Upgrades:  The following list gives an indication of the number of design upgrades experienced by each major system, using the Galaxy-class technology as a baseline:

Spaceframe:                                       15

Inner Hull Plating:                             12

Core Hull Plating:                                6

Outer Hull Plating:                               5

Habitation Spaces:                              8

Consumables Conduits:                    3

Optical Data Network:                       16

Computer Core:                                  23

Auxiliary Data Storage:                     35

Transporter:                                           8

Navigational Deflector:                    12

Communications:                              11

Warp Propulsion:                               29

Impulse Propulsion:                          24

Maneuvering Thrusters:                     3

Lifeboats:                                             15

Defensive Shield Grid:                      18

Shuttlecraft:                                           8

Phasers:                                               13

Photon Torpedo Launchers:             4

-Star Trek:  the Magazine, “Starfleet Technical Database”, pg. 49.  Data Retrieval:  R.M. Sternbach.

                                Even when UFP Starfleet starships are in full production, modification and upgrades are non-stop.  Unlike in the ‘Galactic’ Empire (laughably including a figure the tertiary junior adjutant calls “Emperor Solo”; undoubtedly some stupid Grand Moff that has declared his own territory another ‘Galactic’ Empire, as all the rest before him did), starship research & design is not a cookie-cutter business.  When the Galaxy-class USS Enterprise (NCC-1701-D) was launched (October 4, 2363), it was after the USS Galaxy had been commissioned (back in 2357).  During that time, the USS Enterprise had the following done:


Tests continue on total warp and impulse propulsion systems.  All other internal spacecraft systems powered up; cross-system tests continue.  New flight software installed in all 3 computer cores.  Ejectable bridge module docked.  Minimum flight test program crew completes preliminary training aboard ship.  Captain’s yacht test article docked, nonflight version.  USS Enterprise is launched; leaves dock on maneuvering thrusters.

                        -Star Trek:  the Next Generation Technical Manual, 1.4 Construction Chronology, pg.:  17.  Written by Rick Sternbach and Michael Okuda.


Overview:  Though the USS Galaxy had already proven itself, it’s original software was not utilized in the USS Enterprise.  Note, the chronology didn’t say:

Flight software installed in all 3 computer cores.”

It said:

New flight software installed in all 3 computer cores.”

Clearly, this is indicative of a 2.0, or whatever, showing improvement not only from the USS Galaxy, but, from the production and commissioning of the second starship in the Galaxy-class, as well, USS Yamoto.  There is no indication from any creditable source (the tertiary junior adjutant is certainly not a creditable source, when you see how many lies and intentional misquotations he’s made in the course of his document) stating that Imperial/New Republic/Corporate Sector Authority starship design is anywhere near as painstaking and intricate, nor attention-to-detail oriented.  This is cookie-cutter starship manufacturing, on their part.  Once a design’s proven, start cranking them out, no matter what.  If there’s a problem, it becomes the individual captain’s problem.


Flight test crew continues developmental shakedown trials in Mars space.  USS Enterprise computers receive continuous performance updates from USS Galaxy orbiting Pluto.  Tasks include extensive sensor operations, simulated emergency conditions, simulated combat exercises, and power system stress analysis.  Warp field coils receive first power, nonpropulsive, Warp 1 equivalent.  Power conditioning of warp coils continues up through Warp 8 equivalent.  Performance analysis continuous on all vehicle components.  Main computers developing “systems awareness,” learning and recording how ship behaves as a total entity.  USS Enterprise declared deep spaceworthy and warp-capable.  Yellow warp-stress visibility hull coatings applied.

                        -Star Trek:  the Next Generation Technical Manual, 1.4 Construction Chronology, pg.:  17.  Written by Rick Sternbach and Michael Okuda.

                        Overview:  Flight test crew continues developmental shakedown trials in Mars space.  The USS Galaxy had already gone through all these tests, and yet they continued, doubtlessly, for the USS Yamato, and for USS Enterprise.  Furthermore, not only were these ‘shakedowns’ designed to address any possible or potential problems, but, for “developmental” purposes, as well, meaning that if they found anything new & useful, it would be incorporated into the developing starship, as well as retrofitted into previously completed models (including the Galaxy & Yamoto).  There is no indication that Imperial/New Republic/Corporate Sector Authority starship manufacture involves such extensive, during construction research & development efforts.  For instance, evidence would have it that Imperial/New Republic/Corporate Sector Authority starship design is plagued by engineering incompetence and inability.

  Design flaws plague every high-tech construction, and the Corvette is no exception.  It’s main flaw appears when the ship is used for military applications:  the principle solar collector and stabilizer fin, which is located dorsally amidships, is especially vulnerable to damage from attack.  This small, curved panel is relatively non-vital, controlling only ship maneuverability within planetary atmospheres and collecting solar power for secondary systems and back up power cells.  However, incidental shock waves from direct heavy-weapons hits to the fin can sometimes cause severe vibrations and heat buildup in the main reactor and engine housings, located directly below the stabilizer.  Once this occurs, all systems must be shut down or the vessel risks reactor explosion.  There are many recorded accounts of smaller vessels crippling pursuing pirate Corvettes by repeatedly hitting the stabilizer fin.

To correct this flaw, some Corvettes have been retrofitted with heavier fins and have upgraded the shielding to the dorsal area.  If a captain cannot afford such upgrading, he usually refocuses his existing shields to protect the fin.  This isn’t as good as a total upgrade, but it can keep the Corvette in a battle long enough for it’s speed and maneuverability to come into play.

  -Star Wars, the Role Playing Game Sourcebook, Chapter 3:  Combat Starships, Corellian Corvette, pg.:  30.  Written by Bill Slavicsek & Curtis Smith.  Published by West End Games.  First printing:  November 1987.

What Imperial/New Republic/Corporate Sector Authority engineers consider a ‘correction’ of this glaring design flaw is nothing more that a patch; a Band-Aid for a bullet wound.  Increasing shielding to the area might help prevent it from being hit, but it doesn’t change the fact that the fin is still flawed.  Mounting a bigger fin may make it more robust, but doesn’t change the fact that you’ve just put a bigger target into a flawed system.  The fact that Imperial/New Republic/Corporate Sector Authority engineers would pass this off as a ‘fix’ and that their clients would accept it as such shows the quality of Imperial/New Republic/Corporate Sector Authority starships, as a whole.

  Then, let’s address the other aspects that went into the development of the USS Enterprise:  simulated emergency conditions, simulated combat exercises, and power system stress analysis.”  Again, no indication that Imperial/New Republic/Corporate Sector Authority starship construction crews and engineers put their products through such rigorous testing.  Perhaps the prototypes might go through some similar testing, but it seems that once the prototype passes with a high enough grade, all testing stops.  The Galaxy-class USS Enterprise (NCC-1701-D), even after the Galaxy had proven itself, still underwent simulated combat exercises.  It still underwent simulated emergency conditions testing.  It still underwent simulated power system stress analysis.  Even though, theoretically, it should all be virtually identical to the ship before it, the UFP Starfleet doesn’t accept “theoretically” as an answer with their starships.  Starship captains don’t have to find out in the field that their starships don’t handle very well under emergency conditions.  UFP Starfleet captains don’t have to find out in a firefight that there’s something wrong with a critical system in their ship that is going to get them killed, if they can’t run.  UFP Starfleet captains don’t have to find out in the field that their power systems are going to collapse on them, leaving them high & dry, and calling for help, deep in the frontier.  More than likely, Imperial/New Republic/Corporate Sector Authority starship captains experience this, all the time, and are forced to rely upon their on-board marginally-trained engineers and technicians to ‘fix’ their problems.  Using the Galaxy-class as a baseline, the Intrepid class underwent 29 more revisions into it’s warp propulsion system, and 23 more computer core changes.


USS Enterprise achieves warp flight in outer solar system.  Initial vibration difficulties transitioning to higher warp factors smoothed out by computer adjustments to warp geometry control software.  Skin reinforcements and frame stiffening performed during dock layovers.  Final hull coatings and markings applied.  Live-fire phaser and photon torpedo exercises test crew and systems.  Low-level defensive shield power deficiencies appear; enhanced shield generators designs put into work.  All lifeboats and auxiliary spacecraft docked, including flight-qualified captain’s yacht.  Operational bridge module docked.

-Star Trek:  the Next Generation Technical Manual, 1.4 Construction Chronology, pg.:  17.  Written by Rick Sternbach and Michael Okuda.

  Overview:  The USS Enterprise is put through it’s paces as it’s propulsion system is tested, and when a difficulty is discovered, it’s immediately addressed, not patched like the Imperial ‘engineers’ would.  The warp geometry control software is adjusted, possibly resulting in a new version (x.) or additional revision (.x).  Naturally, these changes are made available to other starship development projects (such as the Intrepid Class Starship Development Project), as well as subsequent ships in the Galaxy class. Using the Galaxy-class as a baseline, the Intrepid class underwent 29 more revisions to it’s warp propulsion system.  Again, we see more combat testing with live fire phasers and torpedoes.  When “Low-level defensive shield power deficiencies appear”, the problem is addressed by an enhanced shield generator design; not with a patch.  Now, this enhanced design is available to the USS Galaxy, Yamoto, and all other ships that can make use of it.  Again, there is no evidence of Imperial/New Republic/Corporate Sector Authority engineers being this thorough, and it is more than likely that if they were in charge of the project, the deficiencies would’ve been discovered out on the frontier, where they would almost automatically become dangerous, even if they were comparatively minor.  Using the Galaxy-class as a baseline, the Intrepid class underwent 18 more modifications to their own defensive shield grid.  It also underwent 15 spaceframe changes, 12 inner hull plating changes, 6 core hull plating changes and 5 outer hull plating changes.  Meanwhile, Imperial/New Republic/Corporate Sector Authority engineering techniques (and engineers) continue to lag piteously behind the in the game.  

(Note also the extensive list of post-launch changes and upgrades to the Enterprise seen here:


v           Glaring lack of computer security  The computer technologies of the Imperial/New Republic/Corporate Sector Authority engineering community are, for all intents and purposes, a joke.  Security is non-existent.  Gigantic starships such as Eclipse-class star destroyers should have cores scores of meters tall, weighing hundreds of metric tonnes.  The amount of physical hardware and programmed software safeguards should be virtually countless.  However, we’re looking at a society that views narrow bandwidth as security, and still uses tapes for data storage.


“The system is quite secure because of the very narrow bandwidth of HoloNet signals:  it is almost impossible to intercept these messages while they are in transit, although tight security must be maintained around HoloNet transceivers themselves to prevent them from being bugged.”

-Star Wars:  the Essential Guide to Weapons and Technology, HoloNet Transceiver, pg:  138.  Written by Bill Smith.


“Nothing sir.  Information retrieval system’s been wiped clean.”

Darth Vader acknowledged this news with a barely perceptible nod. The impenetrable mask turned to regard the officer he was torturing.  Metal-clad fingers contracted.  Reaching up, the prisoner desperately tried to pry them loose, but to no avail.

“Where is the data you intercepted?” Vader rumbled dangerously.  “What have you done with the information tapes?”

-Star Wars “From the Adventures of Luke Skywalker”, chapter 1, pg.:  9.  Written by George Lucas.  A Del Ray Book, Ballantine Books.  Copyright ã 1976 by the star wars corporation


Apparently, no one has thought to develop a narrow-band Subspace transceiver, nor figured out how to scan through selectively narrow Subspace bandwidths.  Nor, even, have they figured out the dynamics of such things as holographic data storage media.  A small robot of the R2-class ‘astromech’ robot was able to hack into the allegedly sophisticated computers of the first production model of the Eclipse-class and wreak havoc.  Entering with a small team of commandos, the robot was able to bypass all security and safeguards and literally bypass the bridge.  With it’s help, the guerilla commandos of the Alliance to Restore the Republic (led by Jedi Knight Cam Solusar) were able to gain control over key systems.  Section 31 surveillance footage captured the team, as well as their dialog:


“Okay, that’s it.  Artoo has bypassed the bridge.  I have control of the navicomputer and the hyperdrive systems.”

“The engines are responding…I just heard the hyperdrive kick in.”

(Unintelligible gibbering from Wookie.)

“None too soon!  Here comes the Empire!  Everybody back to the Falcon!”


On the bridge:


Imperial Navy bridge officer:  “Sir…Eclipse II is beginning to accelerate…we’ve lost the helm.”

Commanding Officer:  “The attack was a diversion!  The rebels are on board this ship!”

The great Imperial flagship accelerates to lightspeed, as Solusar’s team battles their way back to the Millennium Falcon.


From another Section 31 agent (that almost lost his life):


Many light-years away, in high orbit over the Imperial throneworld Byss.


Imperial Officer:  “Engineer Leth, the Galaxy Gun is repaired and ready to fire.  We have found and targeted 50 rebel attack groups, sir…Hiding in deep space.”

Umak Leth:  “Good work!  Notify the Emperor we are ready for his order to commence firing!  The old goat will be pleased that I have fixed his great weapon!”

Imperial Officer:  “Sir--we can’t reach the Imperial flagship.  Fleet command is reporting Eclipse II is under attack.  They are sending a rescue force.”

Umak Leth:  “Hmm…If I fire the Galaxy Gun and save his skin, Palpatine will give me a world to rule…or execute me for disobedience!  It’s worth a chance--commence firing!”


At the moment Umak Leth utters his treasonous command, the Emperor’s flagship emerges from Hyperspace.


Umak Leth:  “My Emperor!  I didn’t mean it!  Eclipse II is going to hit us!  Fire the Galaxy Gun at it!”

Imperial Officer:  “I can’t shoot at the Emperor’s ship, sir…and…uhh…we’re not aimed right!”


With an astromech’s unfailing precision, Artoo-Detoo has set Eclipse IIs navicomputer to the coordinates supplied by Shug Nix and Salla Zend!

-Star Wars:  Empire’s End, #2 of 2, pgs.:  21-24.  Written by Tom Veitch.  Published by Dark Horse Comics, 1995.


So, in a small amount of time, these people were able to gain physical access to a high-criticality system, and take complete control over it, and the rest of the ship, thanks to a small ‘astromech’ robot that’s substantially less useful than a tricorder and a Starfleet engineer.  Any encryption they encountered was, apparently, quite ineffective, complete with weak, easily guessed or neutralized password protection, in clearly marked directories.  The United Federation of Planets takes a much more mature, serious view of encryption and security:


“As all Starfleet communications are normally encrypted, the voice signal pulses are converted by a series of encryption algorithms.  These algorithms are changed on a random schedule by Starfleet Command for galaxywide subspace transmissions, and individual starships codes may be substituted during local away missions.”

-Star Trek:  the Next Generation Technical Manual, 8.2 Personal Communicator, Subspace Transceiver Assembly, pg.:  94.  Written by Rick Sternbach and Michael Okuda.


Standard encryption/decryption, plus enhanced security encryption protocols, are handled by FTL processors within the main computers.  Starfleet encryption algorithms are rotated and updated on a random schedule.  Multiple private key portions are retained with the starship computers, and the public portions are transmitted to Starfleet-issue hardware, such as handheld instrumentation, communicators, personal access display devices and other pieces of expendable gear valuable to possible capture by Threat forces.  Calling for a secure channel on either the spacecraft or remote side will be detected by the main computer, which will place higher encryption schemes in standby mode to await confirmation by command personnel.

-Star Trek:  the Next Generation Technical Manual, 8.3 Ship-to-Ground Communications, Applications, pg.:  97.  Written by Rick Sternbach and Michael Okuda.


“Starfleet private-private encryption keys typically present 2.38 x 10  digit numerical operators for all FTL and sublight speed decryptions, with interlaced changes in the exact numerical arguments to be performed folded into the sequence.”

-Star Trek:  Deep Space 9 Technical Manual, 7.6 Security Considerations, pg.:  71.  Written by Herman Zimmerman, Rick Sternbach and Doug Drexler.


Even private citizenry and corporations have a better handle on computer/communications security than the ‘Galactic’ Empire:


Commercial customers may use their own encryption schemes, restricted only by a maximum of 1.25(10 ) digits in either public or private encryption keys.  Emergency com from either Bajor or the station will be routed by the computer without delay to the appropriate recipients, given the proper com access codes.  All Starfleet military communications with Bajor are conducted according to strict security protocols and filtered through the CPG (see 7.6).  All routine traffic between Starfleet personnel and Bajor is also channeled through the CPG and logged for compression and transfer to Starfleet Headquarters.

-Star Trek:  Deep Space 9 Technical Manual, 7.0 Communications, pg.:  68.  Written by Herman Zimmerman, Rick Sternbach and Doug Drexler.


Prefix Code:  In a Federation starship’s computer systems, the prefix code was a security passcode prepended to computer commands to prevent unauthorized activation or control of key systems.  Kirk gained control of the USS Reliant’s shield systems by transmitting the Reliant’s prefix code from the Enterprise.  The Reliant’s prefix code was 16309.  Captain Picard revealed the prefix code of the starship Phoenix to Cardassian authorities in 2367 when Phoenix captain Benjamin Maxwell was preparing an unauthorized attack on a Cardassian ship.  The code gave the Cardassians the ability to remotely disable the Phoenix’s shields.

The Star Trek Encyclopedia:  a Reference Guide to the Future (Updated and Expanded Edition), Prefix Code, pg.:  384.  Written by Michael Okuda and Denise Okuda, with Debbie Mirek


A 1.25(10 ) digit encryption key (that’s 1,250,000,000 digits) would be something Imperial/New Republic/Corporate Sector Authority computers could not crack in any reasonable amount of time.  It is quite apparent that this civilization that laughably believes it rates anything higher than a 20 on the Weibrand logarithmic development scale still has a long way to go.  The tertiary junior adjutant was even stupid enough to rate the ‘Galactic’ Empire as being superior to the T’Kon Empire of millennia past.  This lack of computer and communications security in their starships and space stations is yet another milestone demonstration of their inability to be rated at anything higher than approximately 20, and another demonstration of how technologically inferior they truly are to the United Federation of Planets.  A science officer with a tricorder could probably crash their entire HoloNet in seconds.


v           Lack of computer sophistication  In addition to their computers lacking any serious semblance of security, their computer power is incredibly low.  A Galaxy-class starship, for instance, is 642 meters in length.  For optimal efficiency, the Galaxy-class has a crew of 1,012.    


-Star Trek:  Deep Space 9 Technical Manual, 14.4 Starfleet Strategic Forces, Starfleet Ship Types Involved in Station-Related Combat, Galaxy-Class Starship, pg.:  151.  Written by Herman Zimmerman, Rick Sternbach and Doug Drexler.

                        Imperial starships of comparable size, due to the inability of their computers to handle as large a workload as UFP Starfleet computers, require a massive amount of crewmen.  For example:


                        Kuat Drive Yards Escort Carrier  Length:  500 meters, crew:  3,505.

                        -Star Wars the Role Playing Game Imperial Sourcebook, Chapter 5:  Capital Ships, Escort Carrier, pg.:  55.  Written by Greg Gorden.  Published by West End Games.


                        Sienar Fleet Systems’ Immobilizer 418  Length:   600 meters, crew:  2,807.

                        -Star Wars the Role Playing Game Imperial Sourcebook, Chapter 5:  Capital Ships, Interdictor Cruiser, pg.:  56.  Written by Greg Gorden.  Published by West End Games.


                        Rendili StarDrive’s Dreadnought  Length:  600 meters, crew:  16, 204.

                        -Star Wars the Role Playing Game Imperial Sourcebook, Chapter 5:  Capital Ships, Interdictor Cruiser, pg.:  58.  Written by Greg Gorden.  Published by West End Games.


                        Clearly, Imperial computer technologies are not up to the task of running complex systems and making complex, rapid calculations, nor are they capable of the parallelism that UFP Starfleet computers are capable of.  So, in order to sop up crew requirements, as is usual for Imperial ‘engineers’, they replace crewmen with robots.  Typical of the Band-Aid mentality of the so-called engineers that make the flying, overpriced, poorly designed, ill-conceived, poorly-tested monstrosities and death-traps that the ‘Galactic’ Empire calls starships.  As opposed to thinking along the lines of making computers that are faster and more powerful, they merely supplement their weakness by adding robots to the mix, in order to free up living crewmen for other tasks that they still wouldn’t have to do, had they a real ship’s computer on the job.  When dealing with such technological simplicities as Imperial starships, it’s no wonder they mass produce them in cookie cutter shipyards at high speed; they don’t require any thought to build, after the first one is rubber-stamped. 

                        While their computers are clearly massive, they, in all likelihood, possess merely a fraction of the memory and processing speeds of cutting-edge UFP Starfleet computer cores, such as those installed in the Galaxy-class, Intrepid-class and the Sovereign-class.  It’s as though their engineering community has reached hit a centuries-long, millennia-long ‘creative block’, somehow preventing them from truly advancing technologies.  Like most Imperial/New Republic/Corporate Sector Authority technologies, they are old technologies exaggerated to the Nth degree.  Superlasers?  They’re just really big lasers.  It’s nothing special.  If one were to design a pistol the size of a small moon that fired continent-sized rounds, they’d do serious planetary damage on impact, if not destroy planets altogether, but does that make it some remarkable technology?  If you rebuild a 20th - 21st century 6-valve (V6) engine the size of a small moon, it would be incredibly powerful, but is this some massive technological leap?  If you build a nuclear power plant that’s the size of a small moon, wouldn’t it stand to reason that the reactors would be extremely powerful?   However, would this represent a massive leap forward for nuclear physics?  No, no & no.  However, the ‘Galactic’ Empire continually deludes itself into believing this and continues to create superweapons that lack any and all real technological innovation, being nothing more than exaggerations of current (and ancient) technologies.  From the Death Stars on down to the Eclipse-class star destroyers, this has been the case.  Imperial starships are the very archetypes of simplicity and technological banality.  Constructing oversized starships and space stations crammed to the gills with these technologies is certainly no special feat.  While ships like the dreadnoughts have cut manpower requirements by substantial amounts; a ‘modern’ dreadnought, equipped with a computer system regarded as ‘modern’ by Star Wars technological standards cuts manpower down to *2,000, but, at the cost of even worse computer security; a single ship could control all linked to their WAN (Wide Area Network), and this has happened.  Through the use of a stupid technology called ‘slave-rigging’ (a glorified combination of remote control and auto-pilot), a crazed, diseased individual (or group of individuals) took control of the legendary Katana Fleet, sending them out into the far reaches of the galaxy, requiring the passage of decades for them to be found, again.  Quite clearly, Imperial/New Republic/Corporate Sector Authority computer technologies are centuries to millennia behind those of the United Federation of Planets Starfleet, as well as many other peer civilizations from the Star Trek galaxy/universe.

                        Then, let’s not forget the utter lack of sophistication in programming languages that the Star Wars galaxy and it’s civilizations labor under.  Binary is still considered big, there.  True, such civilizations like the Bynars still utilize it in the United Federation of Planets, the main reason they do is for psychological reasons.  Bynar thought is binary (yes or no, black or white, etc.).


                        “I need,” the farmer broke in, demonstrating imperious disregard for Threepio’s as yet unenumerated secondary functions, “a ‘droid that knows something about the binary language of independently programmable moisture vaporators.” 

                        “Vaporators!  We are both in luck,” Threepio countered.  “My first post-primary assignment was in programming binary load lifters.  Very similar in construction and memory-function to your vaporators.  You could almost say…”

                        -Star Wars “From the Adventures of Luke Skywalker”, chapter 1, pg.:  35.  Written by George Lucas.  A Del Ray Book, Ballantine Books.  Copyright ã 1976 by the star wars corporation               

                        *-Star Wars:  the Essential Guide to Vehicles and Vessels, Dreadnought, pg.:  42.  Written by Bill Smith.


                        Writer’s Note:  Binary is certainly not a difficult language to master, and even I can understand it with a little looking.  A little while in electronics school taught me that, as well as BCD (Binary Coded Decimal), which utilizes up to 4 digits, while binary’s limited to 3 places.  I certainly don’t need a protocol robot to program things in binary for me, and didn’t have the use of one in school for programming Motorola chips.  While they may be able to speak many languages in the Star Wars storyline, this is nothing special.  If you learn a child, you can learn many, with relative ease.  Even some adults can do it.  Jackie Chan self-taught himself, and now can speak Mandarin, Japanese, Korean, Okinawan, and English, among others.  In Star Wars, the general citizen is incapable of doing too much.  Some can repair starships, but there aren’t too many surgeons; that duty is left to robots.  Apparently, programming responsibilities are also left in the hands of other machines, as well.


v           Lack of technological flexibility  Then, let’s get to the point of the lack of flexibility in Star Wars technologies.  If something is intended for use as a weapon, it, in all likelihood, cannot be utilized for anything else.  In very few instances have Star Wars technologies shown any degree of flexibility and utility any greater than what they were designed to have.  Their engineering community seems completely clueless as to how this could be overcome, and how to improvise in the field, in the first place.  In fact, it would seem as though their ‘engineers’ don’t even realize the benefits of having technologies on board starships that serve in multiple capacities.  Starfleet phaser arrays, such as those installed into the Galaxy-class are capable of a wide variety of functions, not just ‘high power and low power’.  They’ve been utilized to transfer power to a starving spaceborne being that fed on raw energy, as opposed to foodstuffs, and was being held captive at Farpoint Station (Star Trek:  the Next Generation, “Encounter at Farpoint”, episode #1, written by D.C. Fontana & Gene Roddenberry.  Directed by Corey Allen.  Stardate 41153.7).  They’ve been utilized as tunneling instruments, opening cavities into planetary surfaces, without causing mass destruction (Star Trek:  the Next Generation, “A Matter of Time”, episode #109, written by Rick Berman.  Directed by Paul Lynch.  Stardate 45349.1, as well as Star Trek:  the Next GenerationLegacy”, episode #80.  Written by Joe Menosky.  Directed by Robert Scheerer.  Stardate 44215.2).  It’s been utilized as a surgical instrument for the cesarean-style removal of a spaceborne creature from it’s mother’s womb (Star Trek:  the Next Generation, “Galaxy’s Child”, episode #90.  Teleplay by Maurice Hurley.  Story by Thomas Kartozian.  Directed by Winrich Kolbe.  Stardate 44614.6).  The main deflector dish has seen use as both a deflector shield, as well as a heavy particle beam cannon (Star Trek:  the Next Generation, “The Best of Both Worlds”, episodes #74 & 75.  Written by Michael Piller, directed by Cliff Bole.  Stardates 43989.1-44001.4).    Deflector shields were geometrically reconfigured by the USS Defiant and utilized as aerodynamic surfaces when passing through the atmosphere of a gas giant, increasing stability of flight (Star Trek:  Deep Space 9, “Starship Down”, episode #79.  Written by David Mack & John J. Ordover.  Directed by Alexander Singer.  Stardate 49263.5).  The Borg found that they could utilize the main deflector dish as an interplexing beacon that could be utilized to communicate with the Borg Collective back in the Delta Quadrant (Star Trek:  First Contact.  Screenplay by Brannon Braga & Ronald D. Moore.  Story by Rick Berman, Brannon Braga and Ronald D. Moore.  Directed by Jonathan Frakes).  Photon torpedoes have been utilized as instruments to attempt to rekindle solar fusion (Star Trek:  the Next Generation, “Half a Life”, episode #96.  Teleplay by Peter Allan Fields.  Story by Ted Roberts & Peter Allan Fields.  Directed by Les Landau.  Stardate:  44805.3).  The list goes on & on, not only as a testament to the technology, but to the engineers that maintain them.  Star Wars technology may never reach this level of sophistication, because their scientific & engineering communities simply haven’t realized the conditions of deep space may require improvisation that reaches unparalleled levels, and could mean the difference between life & death.  

Back to the Section 31 index