U.S.S. Orleans

Ranger class (Decipher #3)
Ranger class (Decipher #3)

The Ranger class Starship Orleans served as a test-bed for prototype phaser weapons in 2256.[1]

References

Thursday, August 12th, 2010 Games, Library, Ships No Comments

U.S.S. Olympus

Daedalus class (Legacy)
Daedalus class (Legacy)

The Olympus was a Daedalus class starship in the Earth Starfleet during the Romulan War.[1]

References

Thursday, August 12th, 2010 Enterprise, Library, Ships No Comments

U.S.S. Nimrod

U.S.S. Nimrod (STU MVL #4)
U.S.S. Nimrod (STU MVL #4)

The Nimrod was a Daedalus class starship, and was still in service in 2269. It rendezvoused with the U.S.S. Enterprise NCC-1701 following a mission to retrieve the U.S.S. Confederate from the Romulans.[1]

References

Thursday, August 12th, 2010 Library, Original Series, Ships No Comments

Ngultor Ship

Ngultor Ship (EV MVL #1)
Ngultor Ship (EV MVL #1)

The Ngultor originate from a distant part of space. They believe that “the blending of the flesh — the cohesion of species into species — life into life — achieving a single union of wholeness, is a blessed state to be striven for.” The Ngultor vessels encountered by the U.S.S. Enterprise were stranded in Federation space by a warp drive malfunction. They captured several ships for spare parts from the crews before attempting to do the same with the Enterprise. They planned to send harvester vessels to Federation worlds following their return to their home territory, forcing Captain Pike to destroy them.[1]

References

Thursday, August 12th, 2010 Early Voyages, Library, Ships No Comments

Ngultor Mothership

Ngultor Mothership (EV MVL #1)
Ngultor Mothership (EV MVL #1)

The Ngultor originate from a distant part of space. They believe that “the blending of the flesh — the cohesion of species into species — life into life — achieving a single union of wholeness, is a blessed state to be striven for.” The Ngultor vessels encountered by the U.S.S. Enterprise were stranded in Federation space by a warp drive malfunction. They captured several ships for spare parts from the crews before attempting to do the same with the Enterprise. They planned to send harvester vessels to Federation worlds following their return to their home territory, forcing Captain Pike to destroy them.[1]

References

Thursday, August 12th, 2010 Early Voyages, Library, Ships No Comments

U.S.S. Neptune

Defiant class (DS9-537)
Defiant class (DS9-537)

The Neptune was a Defiant class Federation starship. In 2376, the Neptune was commanded by Captain Landwaring and was the flagship of Task Force Javelin, which was sent to locate the source of the Genesis Wave. The Neptune was last heard from in the Boneyard, where it discovered a derelict shuttlepod.[1] The Neptune later arrived, derelict and abandoned, at Myrmidon. Commander Beverly Crusher of the U.S.S. Enterprise NCC-1701-E took a skeleton crew over to the Neptune, where they were infected by an unknown life form, which caused them to attack Myrmidon. The Enterprise transported the crew back aboard, and the Neptune was destroyed by the Genesis Wave.[2]

References

Thursday, August 12th, 2010 Library, Next Generation, Ships No Comments

U.S.S. Monitor (GN22)

Defiant class (DS9-537)
Defiant class (DS9-537)

GN22 “Shatnerverse” Timeline

The Monitor was a Defiant class Federation starship in service in the late 24th century and commanded by Captain John Lewinski. In 2371, the Monitor was assigned a covert mission to destroy the Borg Homeworld. Fitted with a transwarp drive and command temporarily handed over to Ambassador Spock, Captain Lewinsky had the name U.S.S. Enterprise painted onto the hull as a tribute to the ship’s temporary crew. The ship reached the Borg Homeworld in the Delta Quadrant, where it engaged a joint Romulan-Borg armada. The Romulan flagship, the I.R.W. Avatar of Tomed, was destroyed, and the crew discovered the Central Node of the Borg Collective. Although the ship was too damaged to destroy it, James T. Kirk apparently sacrificed himself to destroy the Node, thereby severing the the contection of the Collective. The ship then headed back to the Alpha Quadrant. After returning, its name reverted to Monitor and was returned to its original crew.[1] In 2377, the Monitor was lost with all hands while conducting tests on the transwarp drive, traveling between Starbases 324 and 718 with a skeleton crew of thirty-eight, twenty of whom were warp drive specialists. While conducting the tests, the Monitor was swept into intergalactic space between the Milky Way and Andromeda galaxies. The ship was 350,000 light-years from the Milky Way with an inoperative transwarp drive and a centuries-long return trip home, at warp speeds and with no prospect of resupply, ahead of them.[2] Three years later, the Monitor, which was about to be destroyed by a phenomenon the crew dubbed “The Distortion” (later revealed to have been a “projection” of the Totality) relayed a burst transmission to the Federation by way of the Kelvan expeditionary mission return probes warning them of the threat of the Distortion.[3]

References

Thursday, August 12th, 2010 Library, Shatnerverse, Ships No Comments

Miranda class

Miranda class (Legacy)
Miranda class (Legacy)

Miranda class (ST-02)
Miranda class (ST-02)

A Starfleet fixture of long-range scientific, supply, and exploratory missions for more than a century, Miranda class vessels probably logged more parsecs than any other single Federation vesel class. During the 23rd century, Starfleet Command placed an increasing emphasis on deep space exploration and surveying. The first ships launched after the inception of the exploratory vessel initiative, Miranda class vessels represent the most notable result of Starfleet’s renewed focus on exploration and discovery.[30] First commissioned during the period known as “The Great Awakening,” the Miranda class cruiser was in the forefront of that expansion effort. At the time, Starfleet itself was expanding in response to the changing and expanding economic and political goals of the Federation. To meet the demand of a larger navy, the Military Appropriations Committee authorized the development and testing of hundreds of vessel types, the Miranda among them.[6]

During this same period, the concepts of ship design were rapidly evolving and becoming more sophisticated, and the technology to build and operate starships was going through a revolution. Advances in all facets of the technology required to construct, maintain, and operate a starship were changing so rapidly that some ships were obsolete before they were completed. The Miranda design was changed no fewer than twelve times before the tooling and machining was begun. When these new cruisers were launched, they were only capable of performing three-year missions with resupply at one-year intervals. This made their dual-purpose role of research cruiser harder to perform. With the great distances that had to be travelled, they could not get more than six months travel time from a friendly outpost. This meant they could only advance as fast as the frontier was expanding. The class required some alterations during its trials and was to see many more changes after its commissioning, the last of which was a major refitting in the 2270s similar to that of the Constitution class.[6] Merging a host of diverse capabilities, versatility quickly became a hallmark of the class. Although Miranda class ships would primarily undertake scientific and exploratory missions, certain systems modules were swappable. These Miranda variants enjoyed great popularity in the early 24th century, and their expanded tactical and defensive systems were more than a match for most foes. Ships of this class participated in every major battle of the 24th century, often serving on the secondary or reserve battle lines.[30]

By the middle of the 24th century, Starfleet recommissioned many Miranda class vessels and sent them to surplus depots, scrapped them for parts, or used them as training vessels. Federation member planets and allied systems such as Altair and Betelgeuse first began to add reconditioned Miranda class ships to their own space fleets by the 2360s, after the active production life of these ships ceased. Hence, many Miranda class vessels continued to serve with distinction throughout Federation space and beyond for decades after their theoretical obsolescence.[30]
› Continue reading

U.S.S. Merrimack

Defiant class (DS9-537)
Defiant class (DS9-537)

The Merrimack was a Federation Defiant class starship in Starfleet service in the 2370s.[1, 2] During the Borg invasion of 2381, the Merrimack was part of a task force to defend Starbase 24, along with the U.S.S. Sparta and U.S.S. Ulysses. A previously undetected Borg cube slipped through perimeter defenses and attacked the task force, destroying all three vessels and the starbase.[3]

References

Thursday, August 12th, 2010 Books, Games, Library, Ships No Comments

Makin class

Makin class (FASA-2302)
Makin class (FASA-2302)

Statistics
Length 180 meters
Width 95 meters
Height 35 meters
Mass 102,200 metric tons
Crew 38
Marines 1800
Shuttlecraft 2
Cruising speed Warp 8
Emergency speed Warp 9
Phaser banks 4

The Makin class assault ship could beam down its complement of 1800 marines, 9 heavy tanks, and 32 light support vehicles in 25 minutes, slightly less rapidly than a Continent class vessel. The Makin was produced at the Tellar and Salazaar shipyards, with a combined annual production rate of 14 per year; 68 vessels were constructed between 2275 and 2280.[1]

References

  • [1]FASA-2302: Federation Ship Recognition Manual
Thursday, August 12th, 2010 Games, Library, Ships No Comments