System Access Reference
Systems Nominal
FEDERATION STARSHIP DEVELOPMENT · 12 VOLUMES
STARDATE -255192.3 --:--:--
Fed Chronology · Chapter 12 · Volume 12 — 2276–2295: Towards the Future

12.19 Klingons Threaten War

KLINGONS THREATEN WAR UFP INFONET – 23 APRIL 2287 At a special meeting of the Military Staff Committee earlier today, Klingon ambassador Kil

Klingons Threaten War — p.500
Klingons Threaten War — p.500

KLINGONS THREATEN WAR UFP INFONET – 23 APRIL 2287

At a special meeting of the Military Staff Committee earlier today, Klingon ambassador Kiltarc, of the House of Neygebh, berated the Federation over the delicate subject of the recent mutiny of Admiral James T. Kirk, former Starfleet Chief of Operations.

Behold! The quintessential devil in these matters! James T. Kirk, renegade and terrorist! Not only is he responsible for the murder of a Klingon crew, the theft of a Klingon vessel – see now the real plot and intentions! Even as the Federation negotiated a peace treaty with us, Kirk was secretly developing the Genesis Torpedo! Conceived by Kirk’s son and testdetonated by the admiral himself! … We demand the extradition of Kirk! We demand justice! Remember, there will be no peace as long as Kirk lives!

Federation President Hiram Roth was quick to respond to Ambassador Kiltarc’s demands. He pointed out that Kirk and his followers were currently enjoying asylum on Vulcan under the protection of Ambassador Sarek, who was present at the meeting and also exchanged words with Ambassador Kiltarc. oth then went to on emphasize that as a Federation President R izen Kirk would be tried for his crimes under Federation law, cit not Klingon. At that point Ambassador Kiltarc and his entourage stormed out of the chamber. KIRK SURVIVES COURT-MARTIAL UFP INFONET – 29 APRIL 2287

For most of his career James T. Kirk has been making possible the impossible. He did so again today by surviving the second court-martial in his career, remaining an officer of command rank in Starfleet, and assuming command of a new starship.

Kirk was first court-martialed in 2260 when he was framed for the murder of a fellow officer. The deception was eventuall y scovered and Kirk was cleared of all charges. This time, di however, Kirk’s guilt was obvious. He deliberately violated orders, stole a starship (his former command, Enterprise), accessed a restricted part of space, was responsible for the destruction of the starship he had stolen, engaged in unauthorized combat with a covert Klingon team, and so on. Kirk and his followers were forced to seek asylum on Vulcan , rather under the protection of Ambassador Sarek, an old ally an face charges of mutiny and sedition. Kirk’s conscience th even tually got the better of him, though. It was fortunate for him that his decision to return to Earth coincided with the Wha lesong Crisis.

Kirk ter used his legendary ingenuity to once again save Earth, af whic All h mitigating circumstances were at play in his case. char ion ges were dropped by Starfleet on the orders of Federat Presi rge dent Roth against the mutineers, save for a single cha agai nst Admiral Kirk for disobeying a superior officer. Kirk was bust he way back to captain, which guaranteed he would ed all t never achieve flag rank again. Kirk’s punishment turned out to be a ng in dis ce blessi guise, however. As a captain he could on agai kly n command a starship, which as President Roth quic point ed out was a job for which his talents were best suited.

Acco of rding to reports Captain Kirk has been given command the ch Yorktown, a sister ship of the Enterprise and rebuilt in mu the e same fashion. It has been rechristened as a new Enterpris (with inal the registry of NCC-1701-A) in honor of Kirk’s orig command. Kirk and the new Enterprise left Spacedock today on hat will be the ship’s maiden voyage under its new name. We w can but hope that Captain Kirk and his new starship will continue to protect and serve the Federation as has been the case for so many years.

- 34 -

An unhandled error has occurred. Reload 🗙

Rejoining the server...

Rejoin failed... trying again in seconds.

Failed to rejoin.
Please retry or reload the page.

The session has been paused by the server.

Failed to resume the session.
Please retry or reload the page.