Phoenix Class Fighter

Starship Class Data
Name	AH-12 Phoenix
Type	Fighter/Interceptor
Role	Fighter
Produced	2405-Present
Affiliation	Starfleet
TechStatus	UCIP Canon
Contributor	Wolf

The Phoenix Fighter was designed by 1st Lieutenant John Barstow at the request of the MCS Miramar CO after heavy losses wiped out nearly half the wing. Barstow still fly's the prototype though he's no longer assigned to Miramar.

Table of contents

1 History 2 Technical Summary 3 Detailed Technical Information 3.1 Spaceframe 3.2 Propulsion Systems 3.2.1 Impulse Drive 3.2.2 Warp Drive 3.3 Defensive Systems 3.3.1 Deflectors 3.3.2 Phasers 3.3.3 Projectile Weapons 3.3.4 Hull Armor 3.4 Computer Systems 4 See Also 4.1 Class Variants

History

The Phoenix Class was designed by the MCS Miramar’s Wing Commander 1st Lieutenant John “Apollo” Barstow after losing half a squadron in the Regina 4 campaign. The CO requested a more advanced fighter be designed. The Phoenix was named after the mythical bird that rose from the ashes because of the way the squadron came back from nearly being wiped out. It moves away from traditional fighter design with the engine and weapons placements.

Technical Summary

Spaceframe
Length	8.85m
Mass	14.5 metric Tons
Crew capacity (Standard)	1 Pilot
Propulsion Systems
FTL System	Iroquois M/AM Reactor Core
FTL Standard Cruise	Warp 5
FTL Maximum Cruise	Warp 7.2 for 5 hours
Impulse System	Twin Tandem Impulse System
Standard Impulse Velocity (Full Impulse)	0.77c
Emergency Maximum Impulse Velocity	0.96c
Defensive Systems
Phasers	3 type VII Phaser Cannons (forward facing, 1 each wing tip) 2 Pulse Phaser Cannons (1 each side of the cockpit)
Projectile Weapons	2 x Forward Facing Rapid Fire Micro Torpedo Launchers (1 under each side of nacelle) 1 Forward Facing Quantum Torpedo Launcher (in the forward nose section) 100 13cm Quantum Micro torpedoes Per Launcher 10 Standard Quantum Torpedoes
Deflector Shields	Regenerative Shield System
Other Defensive Systems	10.9 cm Type II Ablative Hull Armor
Computer Systems
Computer Cores	1
Core Type	Type C Bio-Neural Geldisk FTL Core
Operating System	Not in specs
Underlying Technology	Solid state FTL processing
Sensor Systems
Sensors	Standard Navigational Sensor Array Enhanced Tactical Sensor Array

Detailed Technical Information

Spaceframe

Propulsion Systems

The Phoenix has only a single warp nacelle that sits at the aft and on top of the fusel lodge. It is armored so it can take a direct hit with minimal damage. The sublight engines are located below the nacelle and are also heavily shielded. At maximum thrust the Phoenix can reach .96 c. The front and center of the fusel lodge has 2 thruster nasals on each side allowing the fighter to turn on a dime.

Impulse Drive

To be added

Warp Drive

In the simplest of explanations, Matter and Anti-matter are both stored on opposing sides of each other (because of the explosive power they produce when collided) and are brought together in a central chanmber for annihilation. Anti-matter is most unstable, and as such it stored at the bottom with only a deck plate's distance in between for easy dumping.

For more indepth information please see Matter / Antimatter Warp Core

Defensive Systems

The Phoenix has 2 sets of forward facing phasers.

The micro-torpedo launchers are located on either side of the nacelle and can fire 6 micro-torpedoes a second. It also has one quantum launcher located in the nose.

Deflectors

To be added

Phasers

The first set, 3 type VII phaser cannons, are located 1 on each wing and one mounted on the top of the warp nacelle. The second set, 2 pulse phaser cannons, are on either side of the cockpit just aft of it. The arrays can be set to fire together or separately. When linked the array has a fire rate of 3 shots every 4 seconds. When set to fire separately they can fire a shot per second. This is achieved by having the arrays rotate on either the aft 3 or middle 2 cannons. Phaser

Projectile Weapons

The Phoenix carries 100 micro-torpedoes and has a replicator system in the quantum launcher that can replicate up to 10 quantum torpedoes. The replicator runs off of it’s own power source that must be recharged after every tenth torpedo. It was decided to keep it on it’s own power source so that if the fighter was disabled it still would not be totally defenseless. The launcher itself is capable of firing 2 quantum torpedoes every ten seconds.

Hull Armor

Type 2 Ablative Armor: Widely available

Triple layered ablation materials for enhanced control

Standard subsystem energy cost

Approximately 1 meter

For further information please see Starship Armor Types

Computer Systems

To be added

See Also

Class Variants

None

This article is incomplete, it either requires further information, correct formatting or both.