STARFLEET TRANSPORT COMMAND The logistical arm of the Federation Starfleet, Starfleet Transport Command was established as a separate command under the overall control of Starfleet in 2218. Its mission is to coordinate and execute the timely movement of personnel and cargo between starships, colonies and fixed spaceborne installations throughout Federation space. To carry out this mission, it operates a number of supply & storage depots as well as a number of different transport & freighter (cargo ship) classes. Its history appears unremarkable on the surface and detractors are often quick to point out its shortcomings—such as the cancellation of an additional Independence class build group in the years leading up to the Four Years War (a move that nearly brought Starfleet’s war effort to a standstill). However it must be noted that the so-called ‘golden age’ of Federation exploration and expansion during the 23 rd Century would not have progressed, let alone been possible without the existence of such an entity. The turn of the century was a time of transition for all of Starfleet. It was well-known that the Baton Rouge-era starships were little more than stopgaps—testbeds for new engineering techniques and technologies that were being perfected for the next generation of ships which were touted as nothing less than revolutionary. Therefore, up until 2224, Transport Command made do with the J and Y freighter classes as well the Durance class Transport/Tug and an assorted mix of smaller freighters & transports. It was hardly the idea solution, but then again, during this transitionary period, the Federation’s overall growth & expansion was just beginning to pick up.
Transcript
STARFLEET TRANSPORT COMMAND
The logistical arm of the Federation Starfleet, Starfleet Transport Command was established as a separate command under the overall control of Starfleet in 2218. Its mission is to coordinate and execute the timely movement of personnel and cargo between starships, colonies and fixed spaceborne installations throughout Federation space. To carry out this mission, it operates a number of supply & storage depots as well as a number of different transport & freighter (cargo ship) classes. Its history appears unremarkable on the surface and detractors are often quick to point out its shortcomings—such as the cancellation of an additional Independence class build group in the years leading up to the Four Years War (a move that nearly brought Starfleet’s war effort to a standstill). However it must be noted that the so-called ‘golden age’ of Federation exploration and expansion during the 23rd Century would not have progressed, let alone been possible without the existence of such an entity. The turn of the century was a time of transition for all of Starfleet. It was well-known that the Baton Rouge-era starships were little more than stopgaps—testbeds for new engineering techniques and technologies that were being perfected for the next generation of ships which were touted as nothing less than revolutionary. Therefore, up until 2224, Transport Command made do with the J and Y freighter classes as well the Durance class Transport/Tug and an assorted mix of smaller freighters & transports. It was hardly the idea solution, but then again, during this transitionary period, the Federation’s overall growth & expansion was just beginning to pick up.
2221 ushered in the ‘Class I Era’ and with it, radical advances covering every facet of starship design and construction. At the beginning, three initial ship configurations had been laid out—one of which was a standard saucer fitted with two warp nacelles and a tractor-tow pad for use as a transport-tug in concert with a new container family developed in tandem. The Ptolemy class was capable of towing a single container at up to Warp 8 and additional containers (up to a maximum of 3) at gradually reduced speeds. At Ptolemy’s introduction, 5 basic container types were in service: bulk products, liquids, dry goods, refrigerated goods and personnel. In the subsequent decade, additional containers were developed to carry just about every other conceivable cargo type. In addition to Ptolemy, the larger Dolland (based off the Surya class Frigate) and smaller Montojo (based off the Ortega class Heavy Destroyer added much needed flexibility and versatility to the Transport-Tug family). In addition to these versatile Class I vessels, the Independence class holds the distinction of being the first dedicated freighter of the Class I era – introduced in 2229. With a cargo capacity that was unheard of a mere decade before, these ship became critical linchpins in Starfleet’s logistical operations. Over 500 were in service by 2240—this apparently enough for the Federation Council who cancelled 86 planned examples of the Fraternity sub-class that same year. This however, proved to be a fatal mistake. The outbreak of the Four Years War saw these freighters spread thin across critical star systems and they proved to be easy targets as Starfleet devoted comparably little attention to protecting its supply lines. A seventh build group, comprising the Huron sub-class, entered service beginning in 2252. Produced to a modified design, it had a slightly increased cargo capacity, more powerful engines and most importantly—was better protected—featuring a more robust Deflector Shield System and a total of 4 Type VI Phaser Banks compared to the 2 of Independence. This would be the standard to which all further ships would be built for the remainder of the Class I Era. An interesting footnote in this period was the introduction of the Sherman class Cargo Drone. Developed as a stop-gap measure to maintain cohesion in Starfleet’s supply lines during the Four Years War, they operated almost entirely on automation. They were most often used in safe regions closer to the Federation’s core, performing routine supply drops to colonies and small outposts. Despite the fact these ships were unmanned and represented a minimal loss if destroyed, Starfleet decided to concentrate its efforts on the production of larger freighters as well as transport-tugs. A limited number of Sherman class ships were upgraded to the Pershing standard during the Linear Warp era, however none remained in service beyond 2287. Where the transport of personnel (Starfleet & Civilian) was concerned, Transport Command accomplished an incredible amount through the use of only 5 different classes. The Cochrane class, entered service in 2242—nearly all examples being requisitioned for emergency wartime use almost as soon as they rolled out of the dockyards. At 370 meters in length, featuring 5 large hangar bays, able to accommodate up to 2,400 people and carry up to 280,000 metric tons of cargo, it’s not hard to see why. Their size and critical importance made them even more enticing targets for Klingon forces and with this in mind, standard deployment doctrine had these ships organized into convoys, supported by a Destroyer Squadron. Cochrane’s design was something of a departure as well—looking more like a large star liner than a Starfleet vessel. The Aaken class was the next to enter service, in 2248. A smaller counterpart to Cochrane (only 190m in length), it was capable of carrying both personnel and cargo as it’s larger compatriot, but found the majority of its service acting as a freighter (having a max. cargo capacity of 139,000 metric tons). Immediately following Aaken was the Wasp class Assault Transport in 2249. Specially designed and engineered for the SFMC, Wasp was a combination troop transport/shuttlecarrier—able to embark up to 2 Marine regiments (2,592 troops) and up to two squadrons of shuttles or starfighters (24 craft).
In 2271, the SS Mundy was discovered adrift and seemingly abandoned near Starbase 21. The main bridge showed signs of a fierce struggle, however the main computer had sustained damage and the only readable file was a 4-month old Captain’s Log entry—not giving any signs of any emergency or possible danger. A search of the main cargo bay revealed millions of tribbles, which had survived off of food produced by a synthesizer that had somehow remained in operation (how the tribbles got aboard has never been determined). The now-infamous “tribble ship” was taken back to Starbase 21, whereupon an investigation revealed that the ship had been stolen 2 years prior. This mystery remained unsolved until mid 2279, when 2 surviving crewmembers were rescued from a nearby asteroid cluster. Through interviews, it was revealed that the Mundy had been ambushed and boarded by Klingons, who—expecting to find valuable or precious cargo—became enraged when they discovered that tribbles were the only ‘cargo’. They subsequently butchered all but the 2 crewmen, marooned them on an asteroid and set the ship adrift.
The next two classes—Edward and London were conceived and designed in the late 2250’s, at the beginning of what would come to be known as the ‘golden age’ of Starfleet
exploration and expansion. Edward, which entered service in 2261, was the larger of the two—coming in at 420 meters in length, able to accommodate up to 5,000 people and carry up to 575,000 metric tons of cargo. Primarily used as colonial transports, their large cargo capacity and powerful PB-32 series warp engines made them ideal for transporting cargo and/or people over extended ranges.
London was simply a shortened version of Edward, cut down to a length of 205 meters. Originally developed as a Troop/Commando Transport to replace the long serving Texas class, it found use as a short-medium range transport/freighter, gradually supplanting the Sherman class Cargo Drones. A specialized variant—the Hope Class—was also developed for use as a hospital ship.
Taken together, all the above ships helped cement Transport Command’s capabilities and continue to enable and support Starfleet’s exploratory, scientific and defensive
endeavors during one of the most exciting eras of modern space exploration. The advent of the Linear Warp era may have brought about exciting changes for Starfleet’s ships-of-the-line—but for Transport Command, changes were less drastic. This was more
due to the fact that the vessels it operated were designed for a singular purpose, with utility in mind and little, if nothing else. ‘Colonial Transports’—those that could accommodate an extremely large number of passengers—received no attention. Viewed in retrospect, it could be taken as a sign of the times—as the decades passed, the pace of large scale colonization gradually slowed. Many of these once grand vessels were decommissioned and passed into civilian hands while others were requisitioned by the Starfleet Marine Corps and converted into large-scale troop transports.
Starfleet’s Transport-Tug Family evolved in lockstep more or less with the majority of the Class I fleet. The Ptolemy class—severely overworked and never produced to adequate
levels—was uprated to Al-Rashid specifications beginning in 2269. Named for early Federation President Haroun Al-Rashid and the Ptolemy class ship that bore his name (TT 3802), the class maintained nearly identical lines to its older progenitor and quickly became as invaluable to Transport Command as the Enterprise class did to Starfleet.
Capable of towing up to three fully-loaded containers at a nominal cruising speed of warp 6, Al-Rashid helped Starfleet regain a technological edge over its KDF rivals in this
period—the Morast and Tormin (the former having the largest towing capacity of any fleet tug in known space). Lessons learned during the Four Years War also inspired the ASDB to include a heavier armament of 4 Type VII Phaser Banks (1 Dorsal-Forward/3 Ventral-Forward-Port-Starboard). Better armament also equated to better survivability, which meant that transport convoys no longer required the same levels of protection as they did previously—freeing up resources that could be better utilized elsewhere. Additionally, Al-Rashid’s armament combined with its speed and overall agility meant that in certain defensive/offensive scenarios, it could fill the same role as a Destroyer when required.
During the uprating of Moncrief (TT 3800), a small two-craft hangar bay was installed dorsally, on the starboard side of the primary hull. Intended as a trial to evaluate the possible
effectiveness of shuttlecraft use during typical mission scenarios, the concept never really gained traction and was not employed aboard any further ships of the class. The Dolland class, despite its classification as a ‘Heavy’ Transport-Tug, still couldn’t match the capability of either of the two aforementioned Klingon classes (which were equipped
with dual tow-pads and were able to tow more and larger containers). Starfleet’s solution was to take a standard Knox class Frigate, strip it of its phaser cannon hardpoints and affix dual tow pads on the hull’s ventral surface. Modifications beneath the surface included deletion of the port side hangar bay along with the installation of additional fusion reactors to help provide an increased towing capacity that would not overly burden the existing propulsion systems. Upon entering service in 2273, the new Hensley class Heavy Transport-Tugs were capable of towing 2 containers at a nominal cruise speed of Warp 8, 4 containers at Warp 6 and a maximum of 6 containers at Warp 3—making this the fastest, most versatile class of its kind in known space.
The phenomenal success of the Gagarin class Corvette upon its introduction in 2275 made the development and production of numerous variants a veritable certainty. Chief
among those was the Fisher class Light Transport-Tug. Supplanting the Montojo class, Fisher was intended to serve as a short-medium range supply ship. It substituted the unique secondary hull of the Oberth class Scout for a standard tow pad and was capable of towing 1 container at a nominal cruise speed of Warp 5 and 2 containers at Warp 3. Fisher would also hold the distinction of being the last Transport-Tug class to be produced.
The fact that Transport Command’s capabilities were augmented by the further introduction of just one Transport (Sydney) and one Freighter (Ostoris) class underscored both the
success of the new Linear-Warp equipped classes and also harkened to the future. Technological and engineering advances that came together with the launch of the Renaissance class in 2305 dissipated through the fleet and found their way to Transport
Command—launching both the Erewhon class Colonial Transport and the Deneva class Freighter in 2306 and 2310 respectively. As opposed to earlier Colonial Transport types—which were large and could often accommodate hundreds or even thousands of people—Erewhon was remarkably small, just 48
meters long, displacing 2,080 metric tons and only two decks thick. With a maximum rated capacity of only 60 persons—housed in communal, bunk-style accommodations—and a cargo capacity of only 700 metric tons, Erewhon defied every convention about Colonial Transports up to that point. A far cry from the gargantuan Edward class, Erewhon was designed to fit the times—the average size of new colonies dropping sharply since 2277 and hovering between 30-60 persons since 2289. Additionally, the class’ size and capability (rated for a cruising
speed of Warp 5 and able to hold a maximum rated burst speed of warp 7.5 for 8 hrs) made for quick & fast construction times and equally fast deployability—a definite asset where territorial expansion was concerned.
Deneva on the other hand, continued the trend begun by Ostoris, moving away from the traditional transport-tugs, towards more modular designs that could be easily upgraded
and were generally more flexible. Like Erewhon, it was smaller than its 23rd Century contemporary—coming in at only 100m in length and 42,000 metric tons displacement—however, it pioneered the use of a new, modular cargo system that would go on to become a staple of future freighters. It also featured a unique, quad-nacelle arrangement—similar concept to that on the Constellation class—permitting a nominal cruise speed of Warp 7 and a maximum rated burst speed of Warp 9 (for up to 4 hrs), making it the fastest freighter of its size in operation.
From here, the pace of advancement accelerated rapidly, reaching its apex in 2320 with the introduction of the Java class—the largest freighter ever designed and constructed by
a major power. 568 meters in length, the design was based on the modular cargo system introduced on Deneva. The highlight of Java’s design was its long, narrow exo-skeletal ‘spine’ that featured a number of grappling arms extending down on either side. Habitable sections were present forward, amidships and aft containing command and control systems, personnel accommodations and limited support facilities. Its total capacity of 1,270,000 metric tons quickly made it a valuable logistical asset, while like Deneva, Java featured a unique quad-nacelle arrangement—with a nominal cruise speed of Warp 6 and maximum of Warp 8.5 fully loaded (the latter able to be maintained for up to 9 hrs). In a nod to transport-tug classes of the past, Java also featured the ability to carry varied types of containers designed to hold everything from exotic cargoes to passengers (a maximum of up to 20,000 civilians or 16,000 fully-equipped troops).
Transports reached their apex 7 years later with the introduction of the Istanbul class in 2327. 340 meters in length and 18 decks thick, this new transport featured a minimal compliment of just 60 officers and crew. Under normal conditions, it was rated to embark up to 2,500 passengers and 90,000 metric tons of cargo with those numbers rising to 8,000 and 135,000 respectively, during emergencies. A number of docking ports were featured on all 4 sides as well as 5 large shuttlebays which could be loaded with varied types of small craft—usually gravitating towards high-capacity cargo shuttles and runnabouts. Equipped with numerous cargo and personnel transporters and able to make planetfall, Istanbul also proved highly adept in the troop transport and emergency evacuation roles. The final class to be introduced was the Mediterranean class Supply Tender in 2330. Like Erewhon and Deneva, Mediterranean was smaller than the 23rd Century class it was slated to replace (190m long/394,444mT displacement vs the 326m long/546,941mT Griffin class), but was considerably more advanced—featuring a crew compliment that was ¼ of Griffin’s (28), an astonishing cargo capacity for its size (125,000 metric tons) and a robust armament (practically unheard of on a support vessel). With production on all three classes well underway by 2340, Transport Command began withdraw and retirement of older classes in earnest--Ostoris and Sydney the last to be withdrawn in 2345. Starfleet’s simplified, highly streamlined logistics model continued its unimpeded growth and development—not receiving its first serious test until the outbreak of the Dominion War in 2373. Advancements in industrial replication technology lessened the reliance on individual supply depots for the storage, production and transfer of cargoes—the network of 6 massive Ournal II class Space Stations along the Cardassian DMZ (Starbases 257, 310, 211, 371, 47, 129) more than adequate to serve this task in the overall supply chain. Additionally, the fortification of major industrial bases and transfer points left the protection of individual ships and convoys as the only real weak point—a particularly damning one at that, during the war’s early days. With Starfleet lacking the resources to provide consistent convoy protection against the Dominion—whose phased poloron weapons and ‘wolfpack’ tactics inflicted considerable amounts of damage—Transport Command turned to the ASDB, which helped custom design and engineer upgrades that eventually saw classes such as Java equipped with powerful, high-capacity deflector shield generators and those such as Deneva and Istanbul receive highly advanced propulsion upgrades which greatly enhanced their speed and agility.
Late 2374 saw the war’s tide shift back towards the Federation Alliance, the corresponding improvement in the fortunes of Starfleet freeing up yard space which its dedicated Transport arm took full advantage of. Production of Java class freighters was made a top priority, followed closely by smaller Deneva class ships as well as the Istanbul class—which had been co-opted by the SFMC as a troop transport.
With Starfleet and Alliance forces now firmly on the offensive, Transport Command continued the buildup of its own assets in preparation for the full-fledged invasion of the
Cardassian Union and corresponding occupation of Cardassia Prime. Of the 8000 starships allocated to the Invasion, slightly more than half (4,212) were Starfleet. Based on Starfleet deployment doctrine—which has undergone no changes as of this writing—the allocated force of 4,212 Class I starships included a support component of 1,872 Class II vessels (936 Java class Freighters, 468 Deneva class Freighters and 468 Istanbul class Transports)—Transport Command’s largest mass deployment to date. Due to the slower nominal cruise speeds of the
above three classes, the support force did not arrive at Cardassia Prime until nearly a week after the allied fleet—keeping the force safe and intact until operations in the Cardassian home system were concluded. In 2377, a year following the war’s conclusion, Robert DeSoto was promoted to Rear Admiral by Starfleet Command and placed in charge of Federation reconstruction and redevelopment efforts. As part of those efforts, Transport Command Admiral Chaaj became his top logistical advisor, coordinating the scheduling and movement of key cargo shipments as well as related personnel in cooperation with Starfleet Command. One of the first major post war developments for the command involved the construction of Starfleet’s first starbase in the Gamma Quadrant. Located in the Keldanis star system, nearly 90 light years from the Gamma Quadrant terminus of the Bajoran Wormhole, the project proved to be daunting beyond anything previously undertaken. Java class construction was given priority at nearly all of Starfleet’s frontier-based construction yards, with massive convoys (equal in size to the support force used in the Cardassian Invasion) outfitted and equipped at Deep Space Nine before beginning their 5 month journey through the wormhole to Keldanis. In 2380, with highly experimental Quantum Slipstream propulsion technology entering use aboard cruisers of the Vesta class (primarily for testing/evaluation purposes), Transport Command made a formal request with the ASDB for study and evaluation of the technology—the primary benefit of which was the ability to travel infinitely faster than conventional warp drive—for inclusion on the Java and Istanbul classes. However, before any action could be taken, the Borg launched their fateful final invasion in early 2381.
Devastating and/or destroying outright at least 18 Federation worlds and killing billions of Federation citizens, the Command’s immediate task was clear. In addition to reassigning every active ship, tasking them with transportation of relief supplies, evacuating wounded and ferrying reconstruction teams between various planets, outposts and space stations—a number of older classes were hastily refitted and pressed into immediate service. These included the Al-Rashid/Moncrief and Hensley transport-tugs, the Cochrane, Aaken, Edward and Sydney class transports, the Ostoris class freighter and Griffin class supply tender. Additionally, Starfleet’s oldest active vessels—the Constellation class USS Gettysburg and USS Victory—were pressed into emergency relief service as well. Their numbers were such that as conditions gradually improved, the Command’s modern assets were gradually returned to their former duties.
The launch of the USS Excalibur—the first vessel’s of Starfleet’s newest and largest ‘flagship’ class—in late 2381 proved to be a boon to Transport Command, whose assets remained
stretched to the limit for sometime following the invasion. 2500 meters in length, the first production ship to be equipped with a Quantum Slipstream Drive as standard and featuring a cargo capacity of up to 11,179,577 metric tons—the Admiralty’s recognized Excalibur’s value as a transport and freighter immediately, the leviathan spending its first 3 years in service supporting redevelopment and reconstruction efforts.
In 2385, the Command finally found the breakthrough it was looking for—the ASDB certifying Quantum Slipstream Propulsion for use with refit configurations of both Java and
Istanbul, Mediterranean and Deneva being certified the following year. This came none to soon as the Federation Alliance soon found itself embroiled in yet another conflict, this time with an alliance known as the Typhon Pact. To maintain momentum with reconstruction and further bolster the Federation’s still-weak infrastructure, Transport Command shifted all its older classes to the various battlefronts while its modern ones either continued with reconstruction missions, or were being refit.
Fleet commanders balked at first—the notion of having to rely on antiquated support ships seeming patently absurd—however, many soon saw a great tactical advantage in this.
Enemy commanders saw these vessels, which were slower, less advanced and not as well protected or armed, as easy targets. More often than not, adventurous captains would use these vessels—both individually and in convoys—as bait, press their tactical superiority home and score an easy victory.
Thankfully for the Allies, this war was short-lived—ending in early 2387. By the middle of that year, the majority of Transport Command’s assets had been refitted with Quantum
Slipstream drives, accelerating the pace of certain projects—such as the Starbase construction in the Keldanis System, which thanks to convoys reaching the construction site in a matter of days instead of months, was able to be completed a number of months ahead of schedule, in mid 2388 instead of early 2389.
Starbase construction & refurbishment, defensive fortification work and the support of colonization/colonial resettlement initiatives are three of the key priorities Transport Command
has continued to address over the past two decades in addition supporting Starfleet’s exploratory initiatives and continuing to focus on basic infrastructure support and development. As the pace of Federation expansion in the Delta Quadrant continues to accelerate, colonies are planted and new outposts are planned, this vital component of Starfleet is sure to grow both in importance and stature.
Class Classification Service Number Active Length Beam Height Decks
J Freighter 2095-2224 0 339m 140m 59m 8
Mass Compliment Cargo Capacity
855,000 metric tons 15 30,000mT
Armament Defense Systems
2 Plasma Cannons Light Monotanium Single Hull
Class Classification Service Number Active Length Beam Height Decks
Y Freighter 2114-2224 0 280m 76m 53m 10
Mass Compliment Cargo Capacity
634,000 metric tons 23 20,000mT
Armament Defense Systems
1 Plasma Cannon Light Monotanium Single Hull
Class Classification Service Number Active Length Beam Height
Durance Freighter 2130-2224 0 99m 57m 28m
Mass Compliment Cargo Capacity
12,100 metric tons 40 7,080mT
Armament Defense Systems
3 Phase Cannons Light Monotanium Single Hull
Class Classification Service Number Active Length Beam Height Decks
Ptolemy Transport-Tug 2224-69 0 222m 127m 66m 16
Mass Compliment Cargo Capacity
126,500 metric tons 210 Variable; up to 3 containers of varying types
Armament Defense Systems
3 Laser Batteries (2224-49) 3 Type VI Phaser Banks (2249-69) Standard Monotanium Single Hull Standard Deflector Shield System total capacity 54,000 TerraJoules
Class Classification Service Number Active Length Beam Height Decks
Dolland Transport-Tug 2245-73 0 235m 160m 94m 12
Mass Compliment Cargo Capacity
163,000 metric tons 225 Variable; Up to 4 containers of varying types
Armament Defense Systems
3 Laser Batteries (2245-49) 3 Type VI Phaser Banks (2249-73) 2 2nd Class Torpedo Launchers Standard Monotanium Single Hull Standard Deflector Shield System
total capacity 62,000 TerraJoules
Class Classification Service Number Active Length Beam Height Decks
6 Type VIII Phaser Emitters 2 Standard Torpedo Launchers Standard Duranium/Trititanium Single Hull Standard Deflector Shield System
total capacity 440,900 TerraJoules
Mass Compliment Capacity Cargo Passengers
Embarked Craft
83,967 metric tons 28 125,000mT N/A 2
Editor’s Annotations One of the more ambitious projects I’ve taken on has been describing and outfitting the logistical backbone of Starfleet. A necessary component of any full-fledged naval force, especially one like Starfleet, territorial expansion, large-scale construction projects and sustained offensive/defensive operations simply can’t be supported by the personnel, technology and material aboard starships alone. My collection of freighters, transports and other support vessels is a somewhat motley one and along those lines, miscellaneous figures—such as vessel mass, cargo capacity, crew compliment and otherwise—have been estimated by me. Additionally, eagle-eyed readers may note the omission of a class or two in history description, or in the visual identification guide. This is not intentional on my part, just a choice I made to keep things relatively concise.
Bibliography Logo—Kristian “Reverend” Trigwell (Gallery @ Star Trek Minutiae) Visuals—J & Y Classes, Doug Drexler (Drex Files – J and Y) Durance, Todd Guenther & Starstation Aurora (Starship Schematic Database) Ptoelmy, Neale “Vance” Davidson (Jaynz Ships of the Fleet) Dolland, Neale “Vance” Davidson (Starship Schematic Database) Montojo, Neale “Vance” Davidson (Starship Schematic Database) Independence, Geoffrey Mandel (Starship Schematic Database) Sherman, David J. Nielsen (Starship Schematic Database) Wasp, Neale “Vance” Davidson (Jaynz Ships of the Fleet) Cochrane, Neale “Vance” Davidson/FASA (Starship Schematic Database) Aaken, Neale “Vance” Davidson/FASA (Starship Schematic Database) Edward, Neale “Vance” Davidson (Jaynz Ships of the Fleet) London, Neale “Vance” Davidson (Jaynz Ships of the Fleet) Pershing, Eric “Jackill” Kristiansen (Starship Schematic Database) Al Rashid, Neal “Vance” Davidson/Franz Joseph (Starship Schematic Database) Hensley, Eric “Jackill” Kristiansen (Starship Schematic Database) Fisher, Eric “Jackill” Kristiansen (Starship Schematic Database) Overfield, Neale “Vance” Davidson/FASA (Starship Schematic Database) Sydney, Bernd Schneider (Ex-Astris-Scientia) Ostoris, Eric “Jackill” Kristiansen (Starship Schematic Database) Griffin, Eric “Jackill” Kristiansen (Starship Schematic Database) Erewhon, Kristian “Reverend” Trigwell (Thread @ Flare Sci-Fi Forums) Deneva, Kristian “Reverend” Trigwell (Advanced Starship Design Bureau) Java, Bernd Schneider (Ex-Astris-Scientia) Istanbul, Jason (Advanced Starship Design Bureau) Mediterranean, Bernd Schneider (Advanced Starship Design Bureau)
