10 Worst Ever Captains In Star Trek

We are never, ever following these idiots through the breach in Star Trek again

By Sean Ferrick /

There are many things which mark a captain as great in Star Trek, and the franchise has no shortage of people who've earned the description. There are Janeways, there are Siskos, and there are even Boimlers - when the situation really, truly, desperately needs it. Commanding a ship is a big responsibility - something these following people should have tried to remember.

Advertisement

There are traits that a great captain cannot possess if they want to be remembered with honour. One cannot be selfish. One cannot be impulsive to the point of wilful. One must put the lives and wellbeing of the crew under their command first. 

Some of them were tested and they didn't quite match up. Some of them had an unfair set of obstacles in their paths - but proved they were neither adaptable, nor willing to listen to reason. Becoming a captain in the Star Trek universe is supposed to be hard - so one honestly is left wondering how in the name of Boothby did they achieve it. 

10. Captain Benjamin Maxwell - USS Phoenix

While there is an undeniable element of tragedy to his story, as well as a certain degree of thematic vindication that came later on, the irrefutable fact is that Captain Benjamin Maxwell took a Starfleet ship and waged a one-man war. His actions were not simply anaethema to Gene Roddenberry's tenets for Star Trek, but ran the risk of plunging the Alpha Quadrant into a preemptive, bloody struggle.

Advertisement

His justification for his actions was weak. Claiming that 'information came [my] way', he attempted to sway Picard to his way of thinking. The Cardassians, he believed, were absolutely getting ready for a new offensive against the Federation. There was simply no other way of looking at it.

While he may very well have been correct, and the events the followed Dukat's negotiations with the Dominion certainly seemed to prove him right, Maxwell took matters into his own hands. Without any formal declarations, he ordered the Phoenix into Cardassian territory, attacking depots and ships, killing hundreds of Cardassians. This, added with his own personal trauma left over from the massacre at Setlik III, confirmed that, while there may be romanticised songs about the hero who tried to stop a war by fighting one, Maxwell misunderstood what it meant to be a captain in Starfleet.

9. Captain Rudolph 'Rudy' Ransom - USS Equinox

Captain Rudy Ransom was a well-respected officer in Starfleet by the time his ship and crew were whisked off to the Delta Quadrant. There are easy parallels with Voyager's journey, though Ransom becomes the darker side of Janeway's soul, making those decisions that we the audience never thought possible.

Advertisement

How far does one go to get their ship and crew home? In a way, Ransom went above and beyond to ensure the safety of his crew. Yet this argument falls apart when one stops to consider the loss of life along the way - his plan to continue harvesting alien bodies to boost the warp core was shown to be brutal, and to result in near-constant acts of reprisal. These reprisals saw more and more of his crew killed.

Before any of that, Ransom gave the fateful command to ignore the sovereign borders of the Krotonan Guard. This foolhardy act saw half of his crew killed within weeks of their arrival in the Delta Quadrant. When compared with Janeway's command, it is clear that Ransom was the wrong man for the job, with several personality traits that should have seen him flushed out of command training before ever becoming captain of the Equinox.

8. Captain John Harriman - USS Enterprise-B

Beta Canon has done a lot to redeem this young captain in the eyes of Star Trek fans, yet it has also filled in some of the blanks, explaining how exactly he came to command the Enterprise-B on its fateful maiden voyage.

Advertisement

Captain John Harriman was fresh off the assembly line when the new Enterprise encountered the Nexus energy ribbon. He was, to put it simply, completely unprepared to deal with anything out of the ordinary. While Captain Kirk may have been stunned that the ship left spacedock without a tractor beam, frankly audiences were left stunned that the ship left with a man so green in charge.

The expanded universe revealed that Harriman had used his family connections to fast-track him through captains' school, thus effectively abusing his family's position to get himself that first command. As is often the case with untested commanders, people are killed. From history's point of view, Harriman led the mission that saw James T. Kirk KIA, which would leave a black mark against his name for almost a century following.

Harriman's strengths, according to Beta canon, lay outside of starship command and closer to intelligence operations. Some people simply don't suit certain positions. 

7. Fleet Admiral Elizabeth Shelby - Starfleet

This entry is one of the more frustrating on this list, as there were few officers in the fleet who had quite the potential as Elizabeth Shelby. There is no doubt that her expertise and drive are what combined to see her ascend to command the entirety of Starfleet, but at the last hurdle, she seemed unable to see the wood for the trees.

Advertisement

Shelby was the expert when it came to the Borg, proving critical to the survival of the Enterprise-D during the Wolf 359 incident. That officer looked set to command her own ship in a matter of months, having not only earned the respect of her new crew, but of those above her as well.

Nearly thirty years later, Shelby had ascended the ranks to become a five-pip Admiral, commanding the Enterprise-F on her ceremonial final voyage, and had personally supported linking the entire fleet together with a program that was so easily hacked.

Shelby transformed from the bright, incredibly astute expert on the Borg - to become their welcoming party by Frontier Day 2401. She not only accepted, but endorsed, a program that was so obviously Borg-like. Perhaps her ascent was too quick, not allowing for the perspective to follow - but Shelby commanded the fleet on the day it was almost destroyed, seemingly falling to Borg drones in the opening moments of the battle. 

It was a sad end to what should have been a powerful legacy.

6. Captain Tim Waters - USS Valiant

For Tim Waters, school ended rather suddenly, and his crew were the worse for it. Caught behind enemy lines on a training cruise as the Dominion War broke out, Waters and the rest of Red Squad found themselves given field commissions when the officers on board were killed.

Advertisement

One tries to be fair to Waters. He couldn't have any experience, bar what he learned on the go. Perhaps if he had the opportunity to serve as an officer on another starship, observing seasoned commanders in their day to day - but that was not to be his fate. Emboldened not just by his situation, but also by his previous special treatment as part of Red Squad, Waters truly believed he was ready to command.

By the time Jake and Nog arrived on the Valiant, Waters was barely sleeping, using stimulants to remain active in his role. Already breaking under the pressure, he foolishly ordered an attack on the much larger, much more powerful Jem'hadar battleship, sealing both his and most of his crew's fates in the process.

Nog sums it up perfectly as he tries to console Dorian Collins:

He may have been a hero. He may even have been a great man. But in the end, he was a bad captain.

5. Captain Alonzo Vandermeer - USS Ibn Majid

Though only seen in a photograph in Broken Pieces, Captain Alonzo Vandermeer commanded the USS Ibn Majid, Cristóbal Rios's previous posting. When the ship encountered a pair of androids in the Vayt Sector, Vandermeer was ordered to destroy them immediately by Commodore Oh, or face the destruction of the Ibn Majid with all hands.

Advertisement

Not only did Vandermeer comply, but he then took his own life afterwards - all of this without a word of explanation to his crew. The confusion and terror that tore through the ship is embodied in Rios, who left the service, unable to reconcile with what he had seen.

History loves to judge the actions of those who can't defend themselves, but it is rather difficult to fathom Vandermeer not taking a bare second to question this order of execution. If it affected him so deeply that he felt suicide was his only course of action, then this belies Rios's belief that Vandermeer hid behind the pair's android nature to justify his actions. 

Vandermeer, sadly, now has the legacy of a man in such a rush to obey orders that he couldn't stop to think about these orders. This cost him his life, the lives of Beautiful Flower and Jada, and almost cost the sanity of Rios as well. 

4. Commodore Matt Decker - USS Constellation

Captain Decker was assigned command of the Constellation in 2245 and remained her commander until its destruction in 2267. He was considered one of the finest captains in the fleet by the time that Saru went looking for inspiration in Choose Your Pain, receiving a promotion to Commodore in 2263. 

Advertisement

How, then, does a man so promising end up on a list such as this? 

The Constellation's fateful encounter with the Planet Killer utterly broke the man. They engaged the living weapon, only to discover that their ship was outmatched and outgunned. Decker ordered his entire crew to beam down to the nearby L-374 III when the ship lost power, though this condemned them all to death as the unironically named weapon destroyed the world on which they stood.

When Decker was found by the Enterprise, alone on his hulk of a vessel, he initially refused to leave, claiming to have never lost a command before. He then attempted to order the Enterprise to attack the Planet Killer, believing in his madness that this time would be different. He was quickly relieved of his position.

History has mixed views on Decker. His career should speak for itself, yet in his final days he engaged an enemy he was hopelessly unprepared to face, got his entire crew killed, and almost lost a second ship in the process.

3. Captain Clark Terrell - USS Reliant

The events that led to the death of Spock and the creation of the Genesis Planet reached a boiling point as Captain Clark Terrell commanded the USS Reliant. The ship was ordered to scout testing sites for Carol Marcus's Project Genesis, leading Terrell into the clutches of one Khan Noonian Singh. 

Advertisement

When the ship arrives in orbit of supposedly Ceti Alpha VI, Chekov tells him that there is life down there. Terrell opts to beam down, with Chekov - the first officer - to check. Though Terrell is not the only captain in the fleet to make the bizarre decision to send the two highest ranking officers down to an uncharted world, his actions have such immediate and dire consequences that it's difficult not to judge him too harshly.

He is directly responsible, however inadvertently, for Khan's escape. One small measure of mercy is that his crew aren't killed as punishment, though they are marooned on Ceti Alpha V. Terrell pays for his mistake with his life, so it will remain up to the judgement of history as to whether this was deserved or not. 

2. Captain Ronald Tracey - USS Exeter

This writer is in two minds about Captain Ronald Tracey. There is little doubt that his final mission was marred by events that would sully his reputation for the rest of history, though he wasn't a truly evil man, nor even a particularly bad commander. He was, if anything, unlucky.

Advertisement

Tracey, along with his landing party, beamed down to a planet that infected them with a deadly virus. This virus was then brought aboard the Exeter, killing the entire crew. Tracey, down on the planet's surface, survived and came to believe that the planet was akin to the Fountain of Youth.

Tracey differs from Matt Decker, for example, in that the death of his crew was an unforeseeable accident, rather than beaming them directly into harm's way. It was Tracey's actions after the death of his crew that sees him added to this list. His mental state might allow for some sympathy, but he abused his knowledge and technological superiority to gain dominion over the locals.

His is a name that joins an increasingly large list of captains who ruined their entire careers in their last missions. As the saying goes, you're only as good as your last job.

1. Captain J. T. Esteban - USS Grissom

Captain J. T. Esteban was the quintessential 'by the book' commander of the USS Grissom. Assigned to study the newly created Genesis Planet, he was a man so utterly suited to desk work that it is a wonder he ever achieved the rank of captain at all. Perhaps he would be the poster child for 'dot every I and cross every T' - as it is clear he never had an original thought in his head.

Advertisement

When Saavik and David Marcus discover a life-sign on the planet, they immediately request that the Grissom beam it up. Esteban flatly refuses, citing Starfleet regulations preventing him from doing so. To be fair - it is less that he refused to beam the potentially hostile life-form aboard that stands against him but rather the fact he couldn't see passed the book he clung to so dearly.

His actions would probably feed debate for some time to come - did he, technically, do anything wrong on the Grissom's final voyage? Was he merely a man who was less an individual and more an amalgamation of regulations stuffed into a Starfleet uniform?

Whatever the more accurate label, he may end up a footnote in history as the captain who didn't even order his shields raised when a Klingon Bird-of-Prey de-cloaked directly to aft. 

Advertisement