View source for AC-507 Mk I Reaver

{| class="wikitable floatright" style="width: 20%; background: #252525; color: white;" 
| colspan="2" | [[File:Reaver-Mk-I.png|300px]]
|-
| Name:
| Mk I Reaver
|-
| Class:
| AC-507
|-
| Starship Type:
| Federation Warp Fighter
|-
| Production Status:
| Unknown
|-
| Purpose:
| 
* Carrier Based Attack
* Short Range Strike Craft
* Planetary Defense
* Patrol
* Reconnaissance 
|-
| Constructed:
| Antares Shipyards
|-
| Commissioned:
| Unknown (Temporal Anomaly)
|-
| colspan="2" |
|-
| Dimensions:
|
* Length: 21,5 m
* Height: 3,7 m
* Width: 14,9 m
|-
| Mass (w. Standard Armament):
| 23 050 kg
|-
| colspan="2" |
|-
| Technical Specifications
| Advantages
* Unparalleled fighter engines
* Thruster-enhanced handling
* Transphasic shielding 
* Quantitative secondary weapon options
<br>Disadvantages
* High-end weaponry could deplete power quickly
* No internal micro-torpedo launchers
|-
| Standard Crew Complement:
| 
* Tactical CONN Pilot (x1)
|-
| Warp & Impulse Speeds:
| 
Unknown (yet untested)
|-
| Tactical Specs:
|
* (x2) Type XVI Pulse Fire Phaser Cannons (forward-facing)
* (x2) Type X Phaser Arrays (1 forward & 1 aft)
|-
| Defensive Specs:
|
* Transphasic shielding
* Delta 6/D Class 427 Isoton/s Shields
* Type XV Deflector
* 12 cm Type IV Ablative Hull Armour (12 cm OCP)
* Class 4 Structural Integrity Field
* Escape Pod & [[AC-409_Mk_III_Valkyrie#ETS_.28Emergency_Transport_System.29|ETS (Emergency Transport System)]]
|-
| Engine Specs:
|
* Quad-Valravn Reactor Core
* Quad-Valravn Warp Nacelles
* Raven-class 997 Impulse Engine
* Pulsed Reaver-class RCS Thruster Assembly
|-
| Other Systems
| 
* Type E Bio-Neural Geldisk Computer Core
* 7 Module Isolinear Auxillary Core
* (x2) Long Range Subspace Antennae
* (x2) Short Range Subspace Antennae
* (x1) Micro Transporter Cluster
* (x1) Short-Range Tractor Beam Emitter
* Standard Environmental System
|-
|Sensors
| 
* Intuitive Tactical Sensor Suite 
* Class 6/Epsilon Omni-directional Sensors
* Standard Navigational Sensor Suite 
* High Resolution Sensor Range: 6.1 Ly 
* Low Resolution Sensor Range: 28.1 Ly 
|-
| Other Standard-issue Equipment<br> (stored in cockpit)
|
* [[The Accipiter|RG-M1506 PT-10 Accipiter Rifle]]
* Extra rations (16 days)
* (x2) Power cells (for the Accipiter)
|-
| ''Design:''
|
''Auctor Lucan''
|-
| ''3D Model:''
|
''Pinarci''
|-
| colspan="2" | [[File:OVERVIEW-REAVER-MK_I.png|300px]]<br>[[File:Reaver-Hangar.png|300px]]
|}
The '''Mk I Reavers''' were the kind of [[warp]] fighters commissioned to the [[USS Calamity|''USS Calamity'']]. They were first seen outside the Hromi Cluster, where the [[USS Calamity|''Calamity'']] attacked the [[USS Theurgy|''Theurgy'']] and [[USS Harbinger|''Harbinger'']] the first time. Once [[Sarresh Morali]] provided the shield harmonics for the [[USS Calamity|''Calamity'']] and the Reavers both, it was discovered that there were no life-signs found, and the [[warp]] fighters and starship alike were piloted by holographic pilots and crew. 

The original design of the Reavers was not to include holographic [[Tactical CONN]] officers. However, [[Evelyn Rawley, callsign "Ghost"|Evelyn Rawley]] discovered she could commandeer and fly one of them after it was shot down by [[Thomas Ravon, callsign "Razor"|Thomas Ravon]] on [[Theta Eridani IV]]. The shot had destroyed the rigged holo-emitter that held the pilot's holographic matrix, and only the helmet remained inside the cockpit. With the use of TVD - Through Visor Display - Rawley see through the armored and fortified cockpit, and even fly the Reaver into battle. She landed it on the [[USS Theurgy|''Theurgy'']] before the starship ascended from [[Theta Eridani IV]], all the other Reavers were destroyed, giving [[Sten Covington]] and [[Narik Cinsaj]] a project in trying to retro-engineer the fighter before the [[USS Theurgy|''Theurgy'']] would encounter the  [[USS Calamity|''Calamity'']] again.

[[Narik Cinsaj]], however, was raped and murdered by [[Tactical Conn NPCs|Riptor]] before she could even begin the undertaking, with only some light repairs able to be done on it before [[Declan Vasser]]'s mutiny on the [[USS Theurgy|''Theurgy'']]. The [[USS Calamity|''Calamity'']] attacked, and despite [[Captain Jien Ives]]'a orders, [[Theurgy "Thea" NX-79854|Thea]] launched the Reaver into battle with the [[USS Calamity|''Calamity'']], meaning to restore [[Cala]]'s subroutines. [[Theurgy "Thea" NX-79854|Thea]] failed, and the Reaver was critically damaged before the [[USS Calamity|''Calamity'']] was destroyed. [[Miles Renard, callsign "Iron-Fox"|Miles Renard]] towed the damaged Reaver back to the [[USS Theurgy|''Theurgy'']] in the aftermath of the battle, allowing [[Sten Covington]] to resume working on it.

As of the mission to [[Starbase 84]], and with the help from [[Eun Sae Ji]], [[Sten Covington|Covington]] was able to use salvaged parts from other Reavers in order to restore the one sitting in the [[USS Theurgy|''Theurgy'']]'s Fighter Assault Bay. While not completely repaired, it was flight-worthy, but no one had any training in operating the craft, so it was deemed a liability to use in the upcoming mission to [[Starbase 84]]. Nonetheless, the desperate situation of the battle begged for more reinforcements, so despite his lack of training - relying on the computer systems on the craft - Sten "Papa Bear" Covington flew the Cinsaj (named after the late [[Narik Cinsaj]]) into battle, and managed to return the craft aboard without greater damage.

Three days later, the [[Savi]] foraged the Cinsaj from the ''Theurgy'', and it was up to the abductees on the [[Precept]]-ship ''[[The Versant]]'' to take it back, since it remained a piece of critical evidence about the parasitic invasion. 

== Fighter Demonstration 01 ==

<include iframe src="https://sketchfab.com/models/6095c10e1a534f3f9916fa99d3cf9240/embed" width="490" height="380" frameborder="0" scrolling="no" allowfullscreen="allowfullscreen" mozallowfullscreen="true" webkitallowfullscreen="true" onmousewheel="" />

== Production History ==
[[File:Reaver-Opening-Fire.png|left|300px]]Little was known about the origin of this warp fighter, which was not like anything [[Starfleet]] and the [[Advanced Starship Design Bureau]] had made before. Based on findings in the last remaining fighter on the [[USS Theurgy|''USS Theurgy'']], it was constructed at the Antares Shipyards, and the best guess was the incentive of the design and deployment came from the usurpers that overtook the power in Starfleet Command.

As for the design, it was vastly different from that of a [[AC-409 Mk III Valkyrie|Valkyrie]]-line fighter. Instead of the nose-mounted, small navigational deflectors of the earlier fighters, the Reaver had its deflector moved down the the ventral side of the fuselage, where it was often found on normal-sized starships. The fuselage itself was an open design, allowing for a great reduction on hull mass, which granted ability to integrate a quad-nacelle assembly into the fighter's fuselage. The entire fighter was a skeleton hull binding together an unprecedented amount of engine power, and not just in manner of the four nacelles, but also the gargantuan impulse drive monstrosity of an engine in the center aft of the fighter's body. The impulse engine was also complemented with new combustion thrusters on both of the wings, which for a talented pilot offered a lot in the way of combat maneuverability.

Despite its almost frail appearance surrounding the propulsion systems, the entire warp fighter was a well armored construction that was meant to preserve the pilot as well as its sensitive computer systems. Down on [[Theta Eridani IV]], it didn't keep the hull from being penetrated by the atmospheric yield of an AA-grade isomagnetic disintegrator on its highest setting, but in zero-gravity, and if the shield harmonics weren't compromised, the hull could take a lot of punishment before yielding. With the use of TVD - Through Visor Display - the pilot could also see through the armored cockpit, granting no structural weakness above the cockpit area. 

It also appeared as if the advanced technology that the [[USS Voyager]] brought home from the Delta Quadrant in the end of 2378 had made its way to Starfleet's production-lines, since not only did the Reavers have transphasic torpedoes, but also compression phaser cannons and shields with the same phasing technology. While the [[USS Calamity|''USS Calamity'']] did not possess that kind of shielding, the theory goes that transphasic shielding emitters could not be produced in starship-scale just yet, and that the Reavers - being smaller crafts - were fitted with the technology as a first phase. Had it not been for [[Sarresh Morali]]'s revelation of the [[USS Calamity|''Calamity'']]'s and the Reavers' shield harmonics in the first battle outside the Hromi Cluster, or [[Theurgy "Thea" NX-79854|Thea]]'s ability to reveal the updated harmonics in the final battle, the crews of the [[USS Theurgy|''Theurgy'']] and the [[USS Harbinger|''Harbinger'']] would never have survived the encounters they had with the nightmarish starship from the future and her holo-piloted warp fighters.

== External Hard-point Options ==
The fuselage design of the Mk I Reaver and its lesser mass allowed for a large number external wing-mounted hard points during missions, all listed below. The Reavers had two cannon slots on top of the wings, and four slots beneath each wing, giving them a total of 10 hard-point options.

==== Micro Quantum Torpedo Launchers ====
[[File:Torpedo-Launcher-Reaver-Details.png|left|150px]]Torpedo launchers that were mounted in pairs on the dorsal armament rigs on the Reavers. They held 28 micro quantum torpedoes per launcher. This meant that the hard-point option of additional torpedo launchers held 56 mirco-torpedoes since the Reaver itself didn't carry any as standard internal armament. Instead of internally stored quantum micro torpedoes, the Reaver's light and open fuselage design took precedence since it would grant many other optional armament solutions. 

Two of these launchers were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== Mk IV Tri-Cobalt Warhead ====
[[File:Tri-Cobalt-Torpedoes-Details.png|left|150px]] A tri-cobalt warhead was a type of explosive device utilized as a missile - meaning that it was a self-powered guided weapon. Tri-cobalt devices were not standard issue weapons on Starfleet starships, but were sometimes carried in addition to photon torpedoes. A pair of tri-cobalt devices, with a combined yield of 20,000 teracochranes, were used by the ''[[USS Voyager]]'' in order to destroy the Caretaker's Array in 2371. The explosion destroyed the station, leaving only particulate dust, vapors, and metallic fragments. The yield of these warheads could cause subspace ruptures to form, which hampered the mass-production initiatives by Starfleet up until the usurpers took over power in Starfleet Command. It was unknown if these caused tears in subspace, but they were deployed against the ''[[USS Theurgy|Theurgy]]'' during the battle with the [[USS Calamity|Calamity]]. Starship-issue tri-cobalt warheads have a yield of 10,000 teracochranes, whereas these smaller versions have a yield of 3,000 teracochranes. 

Nine of these fighter-sized tri-cobalt warheads were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== Mk I Barghest Cluster Bomb ====
[[File:Barghest-Cluster-Bomb.png|left|150px]]Similar to the nature of a tri-cobalt torpedo. Essentially, this was a torpedo filled with several micro tri-cobalt warheads. Once the torpedo came in contact with an enemy or a surface, it detonated and fragmented into smaller charges, which spread from the point of impact, also exploding on impact, resulting in a large pattern of detonations. Deployed right, this hard-point caused severe damage when scattered upon enemy shield impact. The torpedo snapped open by spring-force, and both the arming and the fuse was pilot-controlled by either manual or automatic settings. It could be armed prior to discharge or scattered by manual command.

Twenty-seven of these fighter-sized tri-cobalt warheads were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== Mk II Transphasic Torpedo ====
[[File:Transphasic-Torp-Details.png|left|150px]]These were phasing high yield shield penetration torpedoes, and a descendant from the torpedoes the Voyager used to make the Borg's transwarp network to collapse.  A single torpedo of the size launched from a starship was capable of destroying a Borg cube. Transphasic torpedoes were, in fact, kept by Starfleet as the weapon of last resort to be deployed to starships only when all else had failed against the Borg. They were the one and only thing Starfleet knew the Borg had not yet adapted to and for that reason wanted to keep this ace in the hole for as long as possible. It was based on generating a destructive subspace compression pulse. Upon detonation, the torpedo delivered the pulse in an asymmetric superposition of multiple phase states. Shields could only block one subcomponent of the pulse. The other subcomponents delivered the majority of the pulse to the target. Every torpedo had a different transphasic configuration, generated randomly by a dissonant feedback effect to prevent the Borg from predicting the configuration of the phase states.

Four of these fighter-sized torpedoes - still carrying a devastating yield despite its inferior size - were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== M-158 Mass Driver Twin Mount Turret ====
[[File:Twin-Mount-Reaver-Details.png|left|150px]]Twin Dual Cannon guns utilising an ammunition replicator to create 30mm tungsten shells. These shells were suspended in a small warp field bubble to render them nearly weightless before being electromagnetically propelled at a speed of 0.025c with a rate of up to 1200 rounds per minute, assuming all four cannons were fired. Devastating against soft targets as well as being effective against armors of nearly all types. However, it was ineffective against shields, and its projectiles could be easily reflected via standard deflector arrays. The weapon could be placed in a fixed forward position or set to automatically track subsonic targets for fire, though it proved to be ineffective at automatically tracking fast moving small targets. It could hit large targets moving at high speeds but not with the same precision as expected with slow or fixed targets. Designed for aerial and suborbital assault on non-shielded terrestrial targets, deep space strikes against bases, and aerial support of ground operations ([[AC-307_Mk_II_Valkyrie#M-142_RF_Mass_Driver_Twin_Mount_Turrets|see also information about the Valkyrie-mounted turrets]]).

Two of these twin-mount turrets were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== Quantum Pulse [[Phaser]] Cannon ====
[[File:Quantum-Pulse-Phaser-Cannons-Detail.png|left|150px]]This cannon complemented the phaser cannons mounted on the Reavers as standard armament. While it drained more power than the regular phaser cannons, these quantum beams had - by comparison - a 150 % damage ratio. They were easily detected mid-battle because of their blue color, much like the light emissions of a launched quantum torpedo were blue too. 

Six of these cannons were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']], but the remaining Reaver could only carry four of them as a maximum depending on other hard-points mounted on it.

==== Type II Tetryon Pulse Cannon ====
[[File:Tetryon-Cannon-II.Details.png|left|150px]]Like the Mk I that was mounted on the [[AC-409 Mk III Valkyrie]], this was an advanced weapon system with two forms of fire. First was a form of a pulse phaser cannon that fired small concentrated tetryon pulses to mark a target. Once marked, the cannon then fired a concentrated phaser shot to cause damage similar to a Starship’s pulse phasers. Its second form of fire was a large concentrated tetryon pulse. This pulse was capable of weakening shields or disabling computerized systems, allowing for the ability to capture vessels without causing major structural damage. ([[AC-409_Mk_III_Valkyrie#Type_I_Tetryon_Pulse_Phase_Cannon|See also information about the Tetryon Pulse Cannon mounted on the Valkyries]])

Three of these cannons were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

==== Mk I Transphasic Compression [[Phaser]] Cannon ====
[[File:TCP-Cannon-Details.png|left|150px]]Like with transphasic shielding (see below) it was discovered that the technology of transphasic torpedoes could be applied in phaser technology as well. At first, the results were disappointing, with little to gain by implementing the technology to directed energy beam weaponry. With a large power drain, robbing the warp systems of power to support shielding, the ambition was almost scrapped at an early development phase. Therefore, new phaser emitter technology was required, and it took time before the idea to compress - to charge - the weapon ahead of mounting them on the Reavers that new ideas sprung forth. With its own power supply to balance the thresholds of the fighter, the cannon was a remarkable piece of engineering. The compression cannon solution favourable, the Mk I Reaver ended up with a high-power shield-penetration beam weapon which, while truly a drain on the warp core despite its own power supply, served a vital tactical role when mounted on the Reavers.

Four of these cannons were available on the [[USS Theurgy|''Theurgy'']] after the final battle with the [[USS Calamity|''Calamity'']].

== Transphasic Shielding ==
[[File:Transphasic-Shield-Animation2.gif|450px|left|thumb|<small>Click image for animation</small>]]After Voyager returned from the [[Delta Quadrant]], it was discovered that the technology of transphasic torpedoes could be applied in deflector shields to create transphasic shielding. Using these principles in shielding, however, first caused a power drain, cutting down [[warp]] and [[impulse speed]] efficiency quite severely. Moreover, it had the potential to quickly burn out shield emitters. Therefore, new emitter technology was required, and it was not until the Mk I Reaver that the solution presented itself. 

Instead of projection-technology, with shield emitters casting the transphasic shielding around the craft, the Reaver instead had nanotech molecular plating installed, but acting as a permanent filament in the armored hull. One might say that the ablative armor lacing in the hull acted as a conduit for the transphasic shielding. The result was a secure, non-volatile projection of the transphasic shield, so while still an energy drain on the craft, it wouldn't cause the shield emitters to burn out. [[Warp]] and impulse capacity was still diminished, and the passive emitter solution did not allow for a completely impenetrable shield either, but still three (x3) times better than regular, contemporary shield technology while activated.

A Reaver could maintain the transphasic shield, energizing the nano-tech molecular plating, for a maximum of ten seconds a time. Between each activation, it would need twice the amount of time activated to regain sufficient power levels. The total amount of shield-time amounted to one full minute per engagement - the Reaver then having to undergo maintenance in order to preserve the integrity of the nano-tech plating. Activating the shield for more time than a total of one minute per engagement might ruin the effect of the shield permanently, if not ruining nano-tech plating cohesion entirely.

[[Category:Technical Specifications]]
[[Category:Fighters & Shuttles]]
[[Category:Temporal Anomalies]]
[[Category:Fighters & Shuttles Specifications]]