writewegrowbeyond - Tumblr blog

writewegrowbeyond · 5 years ago

Text

1. Introduction: Project Akira

After the abortive Borg Invasion of 2366, the Advanced Starship Design Bureau, at the behest of Starfleet Command and the Federation Security Council, fast-tracked development of Project Akira. The initial design brief for Project Akira had been to develop and launch a new multi-purpose heavy cruiser which could replace Starfleet’s ageing Excelsior- and Miranda-class fleets. However, changed astropolitical circumstances meant changed design priorities.

2. Competing Concepts (2366-2368)

The first-generation Akira-class starship was to become a combat-oriented heavy cruiser. Though it would maintain cutting-edge research facilities, the planned class’ operation brief was revised to maximise fleet-support, border defence and fast-strike capacity. The first wave of Akira spaceframes were already under construction at the Utopia Planitia Fleet Yards, Mars, and the Starbase 134 Integration Facility, Rigel VI, and early systems integration and tests would continue as the design teams at the ASDB reconceptualised the class.

The catamaran secondary hull was retained, though the engineering hull beneath the forward command section was shortened, limiting the design’s Y-axis profile. The planned research pod, located between the catamaran hulls, was repurposed as a “battle pod”, to be filled with multiple torpedo launchers and a significant arsenal. Furthermore, all phaser arrays were to be of Type-X, class 2, featuring three times as many emitters as the standard design. The primary hull would be largely given over to fighter bays, marine support and command and control technologies.

To this end, the new class would require miniaturised versions of power plant technology being developed for Project Sovereign in order to meet expected power demands and would feature significantly fewer amenities for embarked crew. Families and attached civilian personnel would not be allowed aboard, and the class’ range would be lower than a standard Starfleet explorer or heavy cruiser, largely limiting the Akira-class starship to operations within Federation space or a fleet context.

However, elements of the design team were not happy with this reconceptualisation. Starfleet’s focus on border-defence and deep-space exploration since the Khitomer Accords in 2293 had seen first the Ambassador-class starship and then the Galaxy-class starship, as well as related designs such as the Nebula-class and the New Orleans-class, take pride of place, while internal Federation operations, including survey, patrol, colony support and resupply missions, were increasingly shifted to an ageing fleet of so-called “workhorses”, including Excelsior- and Miranda-class vessels which were almost a century old.

These designers saw replacing these ships as a vital matter of security for the Federation, as the enormous interstellar state could see its internal supply and communication lines easily disrupted if these older ships were targeted. Supported by some admirals at Starfleet Command and Vulcan’s Federation Councillor, T’Latrek, a number of designers launched a parallel project with Project Akira, codenamed Project Next Step, aiming to make the Akira-class a reasonable stepping point between the Project Sovereign-era development scheme and Starfleet’s long-term plans, including the Project Luna deep-space explorer and the next-generation Project Vesta.

As a result of these changed circumstances, the projected launch date for the class was moved up from 2370 to 2368, with the prototype’s shakedown cruise to be completed by 2369 and the first generation of thirty-six spaceframes to be launched between 2369 and 2371. By 2367 the design was finalised, and systems integration was completed in February 2368. A second generation of sixty spaceframes was tentatively planned for a rolling launch between 2373 and 2378. Project Next Step aimed to have its designs incorporated in this second generation.

3. Launch and Shakedown (2368-2371)

The first starship of the class, U.S.S. Akira NX-62497, was launched in March 2368. The miniaturised Project Sovereign power plant worked well, and in war games and combat trials the starship met or exceeded expectations. However, during the shakedown period it became clear that a combat-focused starship was not conducive to long-term billets, and Starfleet Command implemented a high-changeover roster system, swapping crew out after six- or twelve-month tours of duty. With her shakedown period concluded, Akira returned to Rigel VI for minor refits, before she was officially commissioned and launched in April 2369.

The thirty-six spaceframe first generation of Akira-class starships was launched in three waves of twelve across three years [see appendix A].

The class performed well in the missions to which it was assigned, primarily combat support and patrol along the Cardassian, Tholian, Breen, Tzenkethi and Romulan borders. Still, with no further sign of Borg intervention in Federation affairs, Project Next Step’s work was continued, and the next generation of spaceframes was divided into two new sub-classes: the James T. Kirk-subclass of exploration-focused starships, incorporating Project Next Step’s innovations, and the Akira II-subclass of combat-oriented vessels.

However, there was significant resistance from some in Starfleet Command to this, and it was decided that a testbed vessel would be outfitted to the specifications of Project Next Step before the James T. Kirk-subclass was to be granted final approval for construction. As there were no new spaceframes which could accommodate the testbed due to be launched until 2373, this effectively delayed the launch of the sub-class until 2375, by which time Project Luna and Project Vesta were expected to have entered their final design phases. The delay would therefore render Project Next Step moot.

4. Project Next Step Finds a Home (2371-2373)

In November 2370, while patrolling the Lorenze Cluster, the U.S.S. Trinity was struck by a cloaked radiation mine. Most of the crew was killed, and the ship was badly damaged. Towed back to port, it became clear that the vessel would require a full refit. Due to the influence of Councillor T’Latrek, it was decided that Trinity would become Project Next Step’s testbed. Trinity was diverted to Utopia Planitia, and over the course of 2371 was completely redesigned and rebuilt.

The battle pod was repurposed once again, this time for science and exploration. The sensor technologies developed for Project Sovereign were incorporated into the design, and the ship’s tactical suite was significantly altered. The X-2 phasers were replaced with Type-XII phasers, the ship’s torpedo launcher count was reduced from fifteen to three, and the majority of space given over to fighter bays, marine support and command and control systems were replaced by expanded laboratory facilities, a hospital-grade medical facility and crew amenities.

Crew families and civilians would once again be welcome aboard, and a variable life support system would aim to make the ship welcoming for all of the Federation’s member species. Trinity and the rest of the James T. Kirk-subclass were to have the most diverse crews in Starfleet history, as a pathfinder for the similar goals of Project Luna. To help support this, the ship’s power plant was replaced with the full Project Sovereign design, altered to suit the new multi-mission parameters of the sub-class.

The abrogation of the Khitomer Accords by the Klingon Empire at the beginning of 2372 made many in Starfleet Command hesitant about going ahead with Project Next Step, but the successful launch of Trinity early that year, and her performance meeting or exceeding all expectations during the first months of her mission to the disputed Nikiian Sector along the Klingon border, convinced Command to sign off on the launch of the first wave of the Kirk-subclass: five vessels, alongside five Akira II-subclass counterparts.

5. Trial by Fire: The Dominion War (2373-2375)

These first waves were due for launch in 2373. The performance of the U.S.S. Thunderchild during the Borg attack on Earth during that year led to the renaming of the Akira II-subclass to the Thunderchild-subclass, and the performance of Trinity during that same battle assuaged any lingering fears about the inability of the explorer design to meet combat expectations.

The U.S.S. James T. Kirk herself was refit at Utopia Planitia and launched in June 2373, the de facto lead ship of the new subclass. The first five of the subclass’ spaceframes were named for former captains of Federation starships named Enterprise, and all were in service before the end of 2373. Likewise for the first five Thunderchild vessels, named for the five outer planets of the Sol system.

The outbreak of war with the Cardassian Union and the Dominion at the end of 2373 halted launch of the next planned waves of Kirk-subclass vessels, with the spaceframes earmarked for launch in those years instead fitted out as Thunderchild ships. The planned names of the Kirk-subclass vessels were held over. The 2374 wave of Thunderchild ships was named for significant naval battles in Earth’s history, while the 2375 wave was named for battles of the Earth-Romulan War during the twenty-second century.

The seven launched Kirk-subclass vessels performed admirably during the war, with no losses. While the original Akira-class vessels and the new Thunderchild-subclass ships suffered heavy losses during the war, the large-scale fleet conflicts that characterised many of the war’s largest battles proved perfect for the design and the losses were attributed to merely how often these ships were deployed in heavy combat rather than any inadequacies in design.

At the conclusion of the war, three further waves of both Thunderchild- and Kirk-subclass vessels were confirmed, while the remaining original Akira-class vessels were to be refit to Thunderchild specifications. The 2376 wave consisted of Kirk vessels named for famed Starfleet captains of the twenty-second century, while the 2377 wave was named for twenty-third century captains and the 2378 wave for captains of the twenty-fourth century [see appendix B and appendix C].

6. Victorious in War, Glorious in Peace (2375-2379)

The heavy losses suffered by Starfleet during the war and the demands of reconstruction during peacetime saw many of the Thunderchild vessels serve in support capacities throughout Federation space while the Kirk ships took on exploratory missions as many Nebula-, Galaxy- and Sovereign-class starships were reassigned to peace-keeping or diplomatic efforts. No special naming scheme for further Thunderchild commissions was announced.

There was very little difference between the baseline Akira design and the Thunderchild design, to the extent that it was officially designated Mark 1a. The Thunderchild featured updated systems and elements of the internal layout and power distribution system were altered for greater efficiency, and it was to these specifications that the original Akira-class vessels were upgraded at the end of the Dominion War. Though the original plan had been for thirty Kirk-subclass vessels and thirty Thunderchild-subclass vessels, the reality of war meant that only twenty of the planned Kirk ships were built while forty Thunderchild ships had been launched by the end of 2378.

Ultimately, the original Akira design, the James T. Kirk redesign and the Thunderchild upgrade were classified as unreserved successes by Starfleet Command. Project Next Step was vindicated by the success of the Kirk vessels, as well as the successful launch of the Luna-class long-range explorers in 2379 and the Vesta-class multi-mission explorers the next year. Lessons learnt from the Kirk ships during more than seven years of operation were incorporated into both designs.

7. The Future of the Fleet (2379 onwards)

In 2379, with seventy-eight Akira-class starships of both subclasses still in operation and meeting or exceeding Starfleet Command’s rolling expectations, the Advanced Starship Design Bureau was ordered to develop the Akira-class Mark 3, Sentinel-subclass, which would be launched in 2381 with a refit U.S.S. Sentinel NCC-68455. The new Mark 3 would fully incorporate the Mark 1a and Mark 2 designs to produce a true multi-mission heavy cruiser, purposefully balanced to meet the widest possible range of combat and exploration mission profiles.

The hundred-ship subclass, to be comprised of thirty refit Thunderchild-subclass vessels and seventy newly built Sentinel-subclass starships, would be rolled out between 2383 and 2390, with all refits to be completed by 2385. The end goal of this shipbuilding program was to give Starfleet the capacity to finally retire all twenty-third century starship designs. The projected subclass was expected to serve, with refits and upgrades, until at least the middle of the next century.

The third and final Borg Invasion of 2381 irrevocably altered this program. With Starfleet’s operational capacity reduced by up to forty per cent by the end of the invasion, the shipbuilding program was expanded and accelerated. The refit program was delayed, with only the Sentinel launched at Mark 3 specifications, and the remaining Mark 1, Mark 2 and Mark 1a Akira-class starships were diverted to Federation-wide reconstruction efforts. The Mark 3 Sentinel-subclass program was expanded to one hundred twenty starships, all newly built, to be launched before 2390. The Akira-class Mark 1 and Mark 1a Thunderchild-subclass would be refit to Mark 3 specifications during the final phase of this construction.

The Mark 2 James T. Kirk-subclass vessels were not to be refit as Mark 3 vessels but were to maintain their unique designs. Many of these vessels would continue serving Starfleet into the first decades of the twenty-fifth century, when their spaceframes would begin to reach the end of their operational lifespans.

Appendix A

Notable Akira-class starships

The prototype Akira was refit first as a Mark 1a Thunderchild vessel, before being brought into line with the Mark 3 Sentinel specifications. She was destroyed by the Tholians in 2386, an event which nearly triggered a war between the Federation and her allies and the Tholians and theirs. However, her surviving crew revealed that the destruction had come about as a result of miscommunication rather than naked aggression and averted armed conflict.

The Starship Trinity, the first of the Akira-class vessels to be brought up to the specifications of the James T. Kirk-subclass, was decommissioned in 2399 and sent to the Qualor II Surplus Depot. At that time, she had been commanded by the same officer, Captain Matthew Tye, for the majority of her service since her relaunch in 2372. Both ship and captain were immensely controversial within Starfleet. Trinity served with distinction against the Klingons, the Dominion, the Borg and later in the exploration of the Okeanos Corridor, but Tye developed a reputation for shirking Starfleet orders, most spectacularly in the aftermath of the 2381 Borg invasion when he stole the Starship Hillary for an unauthorised mission.

The James T. Kirk herself was famed for her exploratory missions under Captain Elias Vaughn between 2379 and 2381, when she was badly damaged during the Borg Invasion. While the Kirk was rebuilt and relaunched in 2383, Vaughn himself was killed and many of the crew were reassigned. She served with distinction until 2405, when she was retired with full honours and inducted into the Starfleet Museum. The Kirk would be housed at the Museum’s Orbital Annex above Earth as the prime example of an Akira-class starship.

The U.S.S. Thunderchild served with extraordinary valour during the Borg Invasion of 2373 and subsequently throughout the Dominion War. Unfortunately, she was destroyed with all hands by the Borg in early 2380, during the so-called “supercube crisis”. She was commanded first by Bern Okala, then Evelyn Hoffman and finally Hiroshi Matsuda. Her ten years of service to Starfleet were commemorated with the Thunderchild Memorial in San Francisco.

The U.S.S. Sentinel fought during the Dominion War under Anna Maria Amalfitano, and was instrumental in reconstruction efforts in Cardassian space after the war’s end. Sentinel’s missions at this time are credited as being vital to the eventual Federation-Cardassian alliance, and Captain Amalfitano became an important advisor on Cardassian affairs to Federation presidents for the rest of the twenty-fourth century. Sentinel herself served with distinction until she was decommissioned in 2415.

Appendix B

Akira-class Mark 1 launch schedule

2369

U.S.S. Akira NCC-62497

U.S.S. Geronimo NCC-62501

U.S.S. Gryphon NCC-62502

U.S.S. Essex NCC-62503

U.S.S. Trinity NCC-62504

U.S.S. Black Elk NCC-62505

U.S.S. Singh NCC-62740

U.S.S. Nautilus NCC-62741

U.S.S. Mitterand NCC-62742

U.S.S. Osceola NCC-62743

U.S.S. Meneleas NCC-62890

U.S.S. Nez Perce NCC-62891

2370

U.S.S. Rabin NCC-63293

U.S.S. Templar NCC-63294

U.S.S. Crusader NCC-63295

U.S.S. Capetown NCC-63302

U.S.S. Sharansky NCC-63303

U.S.S. Apache NCC-63304

U.S.S. Ascension NCC-63305

U.S.S. Red Cloud NCC-63306

U.S.S. Thunderchild NCC-63549

U.S.S. Quetzalcoatl NCC-63550

U.S.S. James T. Kirk NCC-63719

U.S.S. Spector NCC-63898

2371

U.S.S. Gettysburg NCC-67430

U.S.S. Fredricksburg NCC-67431

U.S.S. Vicksburg NCC-67432

U.S.S. Antietam NCC-67433

U.S.S. Sentinel NCC-68455

U.S.S. Bondar NCC-68568

U.S.S. Garneau NCC-68569

U.S.S. Kali NCC-68570

U.S.S. Susquehanna NCC-69300

U.S.S. Resilient NCC-69301

U.S.S. Nostromo NCC-69302

U.S.S. Osceola NCC-69303

Appendix C

Akira-class Mark 2, James T. Kirk-subclass launch schedule

2372

U.S.S. Trinity NCC-62504 ref.

2373

U.S.S. James T. Kirk NCC-63719 ref.

U.S.S. Robert April NCC-71261

U.S.S. Christopher Pike NCC-71262

U.S.S. John Harriman NCC-71263

U.S.S. Demora Sulu NCC-71264

U.S.S. Rachel Garrett NCC-71265

2376

U.S.S. Erika Hernandez NCC-75121

U.S.S. Carlos Ramirez NCC-75122

U.S.S. T’Pol NCC-75123

U.S.S. Resthenar sh'Prenni NCC-75124

U.S.S. Chim glav Soach NCC-75125

2377

U.S.S. Philippa Georgiou NCC-76661

U.S.S. Matthew Decker NCC-76662

U.S.S. Satak NCC-76663

U.S.S. Thomas Blair NCC-76664

U.S.S. Atish Khatami NCC-76665

2378

U.S.S. Hikaru Sulu NCC-78241

U.S.S. Margaret Sinclair-Alexander NCC-78242

U.S.S. Walker Keel NCC-78243

U.S.S. Donald Varley NCC-78244

U.S.S. Declan Keogh NCC-78245

Appendix D

Akira-class Mark 1a, Thunderchild-subclass launch schedule

2373

U.S.S. Mars NCC-71266

U.S.S. Jupiter NCC-71267

U.S.S. Saturn NCC-71268

U.S.S. Neptune NCC-71269

U.S.S. Uranus NCC-71270

2374

U.S.S. Salamis NCC-71421

U.S.S. Ecnomus NCC-71422

U.S.S. Puqi NCC-71423

U.S.S. Yamen NCC-71424

U.S.S. Lapanto NCC-71425

U.S.S. Jutland NCC-71426

U.S.S. Leyte Gulf NCC-71427

U.S.S. Pearl Harbor NCC-71428

U.S.S. Coral Sea NCC-71429

U.S.S. Midway NCC-71430

2375

U.S.S. Calder NCC-73551

U.S.S. Tarod NCC-73552

U.S.S. Deneva NCC-73553

U.S.S. Berengaria NCC-73554

U.S.S. Threllvia NCC-73555

U.S.S. Algeron NCC-73556

U.S.S. Gamma Hydra NCC-73557

U.S.S. Prantares NCC-73558

U.S.S. Galorndon Core NCC-73559

U.S.S. Cheron NCC-73560

2376

U.S.S. Androsia NCC-75126

U.S.S. Gallant NCC-75127

U.S.S. Devore NCC-75128

U.S.S. Jaganath NCC-75129

U.S.S. Begin NCC-75130

2377

U.S.S. Norris NCC-76666

U.S.S. Peerless NCC-76667

U.S.S. Aquino NCC-76668

U.S.S. Inverness NCC-76669

U.S.S. Resolution NCC-76670

2378

U.S.S. Poseidon NCC-78246

U.S.S. Virgil NCC-78247

U.S.S. Timberwolf NCC-78248

U.S.S. Rhodes NCC-78249

U.S.S. Mateo NCC-78250

Appendix E

James T. Kirk-subclass deck plans

A. Science module: specialised sensor arrays; module computer core upper level; specialised fusion generator.

B. Science module: observation lounge; module transporter room; probe manufacturing and modification facilities upper bay; science labs; shield generator; module computer core mid-level; probe holding bays; probe launcher

C. Science module: specialised sensor arrays; module sensor control; probe manufacturing and modification facilities main level; science labs; module computer core lower level; batteries.

1. Catamaran: warp plasma supercharger high bay; officers’ quarters.

2. Catamaran: warp plasma supercharger main level; officers’ quarters; catamaran engineering high bay; impulse drive manifolds.

3. Primary hull: captain’s ready room; main bridge; conference lounge. Catamaran: enlisted officers’ quarters; observation decks; antimatter loading distributors; emergency generators; nacelle access; shield generators; impulse fusion generators; impulse drives.

4. Primary hull: secondary sensor array high bay; secondary sensor control; emergency life support; holosuites; escape pods. Catamaran: officers’ quarters; enlisted officers’ quarters; enlisted personnel quarters; deuterium tank high bay; damage control and emergency supply lockers; impulse drive manifolds.

5. Primary hull: primary sensor array; enlisted personnel quarters; research facilities; cryogenic storage. Catamaran: senior officers’ quarters (starboard); VIP quarters (port); officers’ lounge (starboard); VIP lounge (port); officers’ quarters; deuterium tank mid bay.

6. Primary hull: officers’ quarters; holodeck 1 high bay (starboard); holodeck 2 upper bay (port); gymnasium upper bay; cetacean ops high bay (starboard); arboretum high bay (port); laboratory facilities; main crew lounge. Catamaran: officers’ quarters; deuterium tank main bay; shield generators.

7. Primary hull: officers’ quarters; holodeck 1 main bay (starboard); holodeck 2 upper main (port); gymnasium main bay; cetacean ops main bay; (starboard) arboretum main bay (port); hydrological laboratories (starboard); botanical laboratories (port); enlisted officers’ quarters; enlisted personnel quarters; formal dining room and galley (starboard); relaxation garden (port); shuttle command and control.

8. Primary hull: dorsal phaser array; phaser control; enlisted personnel quarters; main security and brig (starboard); sickbay (port); cargo bay 1 upper level (starboard); cargo bay 2 upper level (port), cargo bay 3 upper level (starboard); hydroponics bay 1 (port); stellar cartography lab upper bay (port); main shuttlebay upper level; escape pods

9. Primary hull: main sensor array; main sensor control; laboratory facilities; cargo bay 1 main level (starboard); cargo bay 2 main level (port), transporter room 1 (starboard); transporter room 2 (port); secondary bridge; main computer core upper level; transporter room 3 (starboard); transporter room 4 (port); cargo bay 3 main level (starboard); hydroponics bay 2 (port); stellar cartography lab main level (port); shuttle storage facilities; shuttle maintenance facilities; shuttlebay main level.

10. Primary hull: escape pods; ventral phaser arrays; forward torpedo launchers; torpedo control rooms; torpedo magazines; reaction control thrusters; shield generators; science laboratory complex (starboard) engineering laboratory complex (port); computer core upper mid-level; chief engineer’s office; main engineering high bay; industrial replication and fabrication upper level; reaction control thrusters and fuelling bays.

11. Primary hull: forward observation lounge; public galleys; cryogenic storage; tertiary sensor arrays; secondary security (starboard); secondary sickbay (port); computer core lower mid-level; main engineering main floor; swimming pool (starboard); gymnasium (port); dilithium intermix chamber; industrial replication and fabrication main floor.

12. Primary hull: battery compartments; science lab complex; main library centre; computer core lower level; emergency transporters; rear torpedo launcher; torpedo control rooms; torpedo magazines.

13. Primary hull: battery compartments; deflector array upper bay; deflector control; science lab complex.

14. Primary hull: main deflector array; emergency crew quarters; crew lounges.

15. Primary hull: antimatter storage; warp core ejection mechanism.

0 notes