Hello and welcome to another episode of Truth OR Myth Beta Canon, a Star Trek web series that dives into the history of any given topic using Beta Canon sources using my own imagination to fill in the gaps, and create a cogent narrative. In today’s episode, we’re continuing our look at some of the other Galaxy Class Starships and their Beta Canon histories.
Because this IS a Beta Canon video, all information relaid should pretty much be taken with a grain of stardust, and only considered a little bit of Star Trek Fun! And so, with all that out of the way, let us begin.
One of the most influential starships of the 24th Century, the U.S.S. Enterprise – D, under the command of Captain Jean-Luc Picard, would blaze its own trail into the history books. But what about the other Galaxy Class starships? Well today, we find out…
The U.S.S. Yamato was the second Galaxy Class starship to be constructed and launched in 2363. Originally launched with a Registry of NCC – 1305 – E, to pay homage to the Original Shepard Class U.S.S. Yamato, this was changed quickly after a Yamato – D scandal came to light.
Believed to have been destroyed by a subspace anomaly in 2351, The Yamato – D would re-emerge from that anomaly in the year 2365. The Captain and Crew of the Yamato – D then proceeded to begin systematic attacks on both Federation Colonies and Starfleet Starships. These attacks would garner a loss of life of almost 100.000 officers, crew members and civilians.
Left with no choice, Starfleet would send an Armada to hunt down and destroy the Yamato – D, and after an intense firefight, the U.S.S. Yamato D would in fact be destroyed.
Investigations into the incident discovered a previously unknown form of radiation left in the area where the Yamato – D had exited the Subspace Anomaly. And Subsequent testing of this radiation discovered that it had a negative effect on the ethical parts of the humanoid brain, cause a form of evil insanity. Although the Crew of the Yamato – D had been exonerated of willful mass murder, Starfleet Command would decide to immediately change the Registry Number of the Yamato – E, giving it the more generic registry number of NCC – 71807.
Its then Captain, Donald Varley, used his sway and position in Starfleet to keep the name as the U.S.S. Yamato, vowing to restore honour to that ship name. And its registration plaque would be changed to reflect Varley’s view with the motto “I have sworn eternal hostility against every form of tyranny over the mind of man” added by the Captain.
Early in 2365, the Yamato had been under the command of Captain Richard McKenzie, and the U.S.S. Yamato was assigned to patrol sector 134 near the Romulan Neutral Zone. Unfortunately, during this patrol, the U.S.S. Yamato would discover a derelict Daedalus Class Starship, the U.S.S. Alto, believed to be destroyed in 2166, in an asteroid belt of system game Hydra 4.
Captain McKenzie, not being one to follow Starfleet Policies, lead an away team over to the classic starship in an attempt to restore its systems and unravel its mysteries. During this mission, the away team would discover the crew of the Alto had contracted an unknown fast-acting virus which had killed them all and given communication methods of the time, and the radiation contained within the system, they were unable to inform Starfleet Command of what had happened.
Captain McKenzie and his crew then unwittingly brought the Virus aboard the Yamato, and before a cure was found, over half of its crew had been killed by it, including the Captain and its First Officer.
During this trip to back to Earth, it was then that the Yamato – D incident occurred and after it arrived at Earth, Captain Donald Varley assumed command of the Yamato. But the Yamato’s streak of bad luck would not end there.
Late in 2365, the Yamato was destroyed with the loss of all hands in the Romulan Neutral Zone. Her destruction was caused by an Iconian computer virus that had been transmitted to the Yamato by an ancient Iconian probe. This virus spread through the ship’s systems attempting to re-write its operating code and as a result, eventually caused a failure in the matter/antimatter control systems, destroying the starship before Captain Jean Luc Picard and the U.S.S. Enterprise D, who had responded to the Yamato’s distress call, we’re able to help to fail vessel.
After its destruction, Starfleet Command would make the decision to retire the Name Yamato from its starship registries, and as such, no further U.S.S. Yamato’s were commissioned.
The U.S.S. Venture NCC-71854 was constructed and launched from Utopia Planitia in 2366.
The U.S.S. Venture would also have the bizarre honour of being recreated as the command starship at Starfleet Academy for its Kobayashi Maru Tests from 2366-2372.
In the year 2368, the U.S.S. Venture made an emergency stop at the Starfleet facility on Luxor IV after discovering a malfunctioning baffle plate. Though a thorough investigation was conducted, the outcome determined the malfunction to be caused by a defect in the plate itself, rather than sabotage.
In 2370, the Venture was sent to the New Bajor colony to search for survivors after the Dominion Claimed to have destroyed the colony. Upon its arrival, it was quickly determined the Dominions claims were ruthlessly accurate, with only 7 survivors of the massacre.
In 2371, the U.S.S. Venture was one of three starships assigned to bolster the 20th Fleet based at Starbase 364 and protect that sector from suspected Dominion incursions.
In 2372, under the Command of Captain Roger Corbett, the Venture was on a diplomatic mission when it received news that Klingon forces were massing to attack Starbase Deep Space 9.
Captain Corbett then volunteered to lead and then assembled a small task force to protect the station from this renewed Klingon Aggression. Temporally delayed after a small Battle Group of Klingon ships attacked the task force, the Venture would not only defeat those Klingons but make it in range of Deep Space 9 which then allowed Sisko to use Corbett’s task farce as a bargaining chip to end the Klingon Attack on the station. After the incident, Captain Corbett would be promoted to the rank of admiral, and given command of the 4th Fleet.
In 2373, the Venture took part in a scientific expedition to the Holaren Nebula under the temporary command of Captain Benjamin Dawson. Later that year, Permanent Command of the U.S.S. Venture was given to Captain Allera Stanley.
From that point on, the U.S.S. Venture was heavily involved in the Dominion War effort, participating in many of the major operations against ruthless enemies. The Venture participated in Operation Return, the epic battle to recapture Deep Space 9 from the Dominion and she was one of the first ships to arrive at the station after Captain Benjamin Sisko and the U.S.S. Defiant forced the Dominion into retreat.
The Venture also participated in the First Battle of Chin’toka in late 2374, helping the allied forces capture that system. After the Dominion War, the U.S.S. Venture lead a joint Federation-Klingon task force, ordered to clean up Renegade Cardassian forces that refused to accept the Unions Surrender.
By 2380, the U.S.S. Venture had become a luxury transport ship, ferrying diplomats and prospective Federation Member world delegations to various meetings through out the Federation.
During the Borg Invasion of 2381, the Venture led a fleet defending the Andorian system against the Borg and eventually was able to route the Borg Forces that were attacking Andor.
In 2383, the U.S.S. Venture would be assigned to Deep Space 9 where it would engage in several patrol duties for the Newest federation Member World.
The U.S.S. Magellan NCC – 71820 was the first Galaxy Class starship to be fully constructed with the new refit technology from the ground up. As a result, the Magellan would have an extended shakedown cruise in order to ensure all the bugs were worked out from this updated class.
In 2370, the Magellan was assigned to investigate the disappearance of the U.S.S. Alcubierre in the Elicona sector. After its recovery, the Magellan towed the Alcubierre to Starbase 117.
In the year 2374, the Magellan participated in Operation Return to retake Deep Space 9 from the Dominion. The Magellan, along with the U.S.S. Venture was assigned to protect the U.S.S. Defiant, but due to the overwhelming Dominion forces, and the damage both ships had taken, the Magellan was unable to follow these orders.
In 2376, the Magellan participated in the resolution to the Iconian gateway crisis. In an effort to reach the Iconian Gateway in time, its Captain ordered speeds from the starship which pushed it past the red line.
As a result, one of the Magellan’s Dilithium crystal relays blew out, but even so, its chief engineer was able to keep the starship together and its engines past the red line. Of course, once out of warp it was discovered that the Magellans engines were severely damaged, and after the successful mission to destroy the Iconian Gateway, the USS Magellan would travel at low warp to Starbase 193 for extensive engine repairs.
Currently, the U.S.S. Magellan has been assigned to the Starfleet Corps of Engineers as a test vessel for a new Classified Propulsion technology.
In the 2360s the Galaxy Class would be seen by most of the Federation Public as the height of hubris on Starfleet’s part.
But once refit with new technologies developed after the Battle of Wolf 359, the Galaxy Class would become a major staple and fighting force for Starfleet and the Federation, earning the USS Yamato, though sadly, and the USS Venture and the USS Magellan their places, in Starfleet History…
Thank you for watching today’s episode of Truth or Myth, what do you think of the Beta Canon history for these Galaxy Class Starships? Do you want to see the Galaxy Class make a more prominent showing in Star Trek: Picard? Well leave your comments in the section below and don’t forget to like the video and subscribe to the channel.
Want to help the channel participate in classified tests on a new propulsion system? Then just click HERE to become a channel Patron…
Watch The Latest Truth Or Myth Below
Thanks again for watching, Live long and prosper…