FANDOM


Created by CaptFredricks
I'm a doctor
I'm a doctor, not an encyclopedia!
This article or section is missing key information on the discussed subject. You can help Federation Legacy Wiki by expanding this article to conform with wiki standards.

Charles Francis Morgan V was a Human Starfleet officer who served in multiple fashions aboard the USS Leviathan, most notably as its operations officer and transporter chief.

Biography Edit

Early life Edit

Charles Morgan V was born on 24 August 2386 in Greenwich, England, Earth to Francis Morgan.[citation needed]

Academy years Edit

He graduated from Starfleet Academy in 2408, though he was absent from the graduation ceremony.[a][citation needed]

Starfleet career Edit

Charlie was assigned to the USS Leviathan in 2409 as a junior officer.[citation needed] On stardate 83164.0, the Leviathan was attacked by the Klingon vessel IKS Chot. After Koja Nara, the operations officer, was killed at her station during the attack, Charlie took her place.[1]

When Dylyp Azeli was assigned to the Leviathan as the new ops officer, he inherited the position of transporter chief.[2]

Appendices Edit

Background and trivia Edit

  • Charlie did not have a first name in the original draft of "Khitomer Crisis". He was added to the chapter as simply an extra member of Jason Fredricks' away team to the USS Khitomer. CaptFredricks liked him enough to keep him as a recurring character and again included him in "Stranded in Space".
  • Charlie was originally meant to be from West Virginia, but CaptFredricks decided to make him British instead.

Appearances Edit

Unofficial appearances

Notes and references Edit

  1. It is possible that Charlie was in fact present at the ceremony, and his name was called behind Jason Fredricks and Lucas Wells' dialog.

Navigation Edit

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.