- For other uses, see Exeter.
|Launched:||reference stardate 1/9003|
|Status:||succeeded in name by Constitution-class USS Exeter|
The Exeter, with an assigned registry number of NCC-1706, was one of the initial batch of Constitution-class starships that were ordered for Starfleet appropriation on stardate 0965. (TOS reference: Star Fleet Technical Manual) She was built to Mk I specifications and was launched on reference stardate 1/9003, entering service with a new registry number, NCC-1672. (FASA RPG module: Federation Ship Recognition Manual)
At some point in the early 2260s, the Exeter was largely responsible in putting an end to Klingon harassment of Federation shipping along the Federation-Klingon border. (TOS - Errand of Fury novel: Sacrifices of War)
Ensign Kevin Riley was assigned to the Exeter as a navigator in 2262, following his graduation from Starfleet Academy. He remained aboard until 2265, when he transferred to the USS Enterprise. (ST video game: Starship Creator)
Later that year the Exeter was assigned to a sector near the Romulan Neutral Zone. Following rumors of a build-up of a Romulan invasion of the Federation and the supposed disappearance of the Enterprise, Admiral Jake Iota assigned the Exeter to a task force (including the USS Farragut, USS Potemkin, USS Hood and six scout ships) that were to proceed to the Neutral Zone to investigate, under the joint command of Iota and Captain Mikel Garson of the Potemkin. (TOS novel: Web of the Romulans)
Admiral Withrow recalled the Exeter to support Enterprise during the Kenisian - Maabas situation. But the Exeter was three weeks from Enterprises position.(TOS NOVEL: Crisis of Consciousness)
In 2268, the Exeter visited the planet Omega IV on a survey mission. Captain Tracey led a landing party to the surface and discovered two groups of people, the Yangs and the Kohms, at war with each other. Tracey remained on the surface to talk to the Kohms while the rest of the landing party returned to the Exeter, the crew soon fell to a mysterious disease. Tracey survived on the surface, and believed that Omega IV was a fountain of youth and good health. His illusions were shattered, however, when the USS Enterprise responded to the distress call, and eventually arrested Tracey for violating the Prime Directive. (TOS episode: "The Omega Glory"; TOS novels: Ex Machina, Garth of Izar)
Following the incident on Omega IV, the Enterprise recovered the abandoned Exeter and towed her to the nearest starbase where she was decontaminated and recrewed and eventually returned to active service. Captain Douglas Newman was also appointed as the ships new commanding officer. (Decipher RPG module: Starships; TOS novel: First Frontier)
- According to FASA RPG module: Federation Ship Recognition Manual, the Exeter was scrapped soon after her recovery, on stardate 2/1012.
Shortly afterwards, the Exeter was assigned to participate in war games alongside the Farragut and the Enterprise near Izell, in order to test the new warp-powered shield technology that had been installed aboard the Enterprise. (TOS novel: First Frontier)
The following year, the Exeter was assigned to transport two warp nacelles that were originally destined for the USS Intrepid, to the Enterprise, while she was undergoing extensive repairs in orbit of Talin IV. (TOS novel: Prime Directive)
In 2270 the Exeter was assigned a month-long protection duty of the planet Gateway. The Exeter's crew were informed that they were guarding an important archaeological site. They were eventually relieved by the USS Potemkin. (TOS - The Yesterday Saga novel: Yesterday's Son)
Shortly after the Exeter, now under the command of Captain Andreoni, assisted the Enterprise, the USS Majestic and the USS Yorktown in keeping an experimental transwarp drive from falling into enemy hands. (TOS - Fortunes of War novel: Battlestations!)
In 2273 the Exeter was operating in sector 001 when she was reassigned, along with the USS Potemkin, to deal with the Albasynnia affair. Rear Admiral Kirk had advised Admiral Heihachiro Nogura against sending both starships on the grounds that it would leave the sector largely undefended. Nogura overruled him, but Kirk was later proved correct when the V'ger cloud entity moved towards Earth. (TOS - Crucible novel: Provenance of Shadows)
USS Exeter personnelEdit
- commanding officer:
- chief medical officer: Commander Carter (c.2268)
- navigator: Ensign Kevin Riley (2262-2265)
The Exeter first appeared in the episode "The Omega Glory", in the second season of TOS. The appearance of USS Enterprise onscreen with Exeter was the second of three times that Enterprise ever appeared simultaneously with another vessel of the Constitution-class (in the original, non-remastered, Star Trek releases).
In non-canon, Exeter was first given a registry number, NCC-1706, in Franz Joseph's Star Fleet Technical Manual. When FASA RPG module: Federation Ship Recognition Manual was released, they used the registry NCC-1672, based on a system assigning known starship names with a registry list seen in episode "Court Martial". This assertion was made by Star Trek fan (and future FX modeler) Greg Jein, and published in fan magazines. When the Star Trek Encyclopedia was published, over a decade later, editors Michael and Denise Okuda used Jein's Exeter registry. Jein's registry list, with some modifications by Okuda, is also being honored by official productions, such as the remastered TOS.
To date, the NCC-1706 registry has not been used in any more licensed publications, but is popular in fan fiction. Under Michael Okuda's direction, the NCC-1672 became the official "canon" registry in 2007 with the broadcast of the remastered version of "The Omega Glory"
|Ships named Exeter|
|Federation, Starfleet||USS Exeter (NCC-1672, Constitution-class) • USS Exeter (NCC-1712, Constitution-class) • USS Exeter (NCC-1788, Class J starship) • USS Exeter (NCC-2016, Excelsior-class) • USS Exeter (NCC-26531, Ambassador-class) • USS Exeter (Galaxy-class) • USS Exeter (NCC-1672-C, Exeter-class)|
| Imperial Starfleet|
|ISS Exeter (NCC-13701, Exeter-class)|