AC-409 Mk III Valkyrie: Difference between revisions
From Star Trek: Theurgy Wiki
Auctor Lucan (talk | contribs) No edit summary |
Auctor Lucan (talk | contribs) |
||
(113 intermediate revisions by 5 users not shown) | |||
Line 1: | Line 1: | ||
{| class="wikitable floatright" style="width: 20%; background: #252525; color: white;" | {| class="wikitable floatright" style="width: 20%; background: #252525; color: white;" | ||
| colspan="2" | [[File: | | colspan="2" | [[File:OVERVIEW-VALKYRIE-MK-III.png|300px]] | ||
|- | |- | ||
| | | Name: | ||
| | | Mk III Valkyrie-class | ||
|- | |- | ||
| | | Model: | ||
| | | AC-409 | ||
|- | |- | ||
| Starship Type: | | Starship Type: | ||
| | | Federation Warp Fighter | ||
|- | |- | ||
| Production Status: | | Production Status: | ||
| | | Prototype Testing Stage | ||
|- | |- | ||
| | | Role: | ||
| | | | ||
* Space Superiority Craft | |||
* Planetary Defense | |||
* Carrier Based Attack | |||
* Patrol | |||
* Reconnaissance | |||
|- | |- | ||
| Constructed: | | Constructed: | ||
| | | Antares Shipyards | ||
|- | |- | ||
| Commissioned: | | Commissioned: | ||
| | | October 9th, 2378<br> Same as the [[USS Theurgy|''USS Theurgy'']] | ||
| '' | |||
|- | |- | ||
| colspan="2" | | | colspan="2" | | ||
Line 35: | Line 32: | ||
| Dimensions: | | Dimensions: | ||
| | | | ||
* Length: 20 | * Length: 20.5 m | ||
* Height: 3 | * Height: 3.5 m (w. landing gears extended) | ||
* Width: 13 | * Width: 13.7 m | ||
|- | |- | ||
| Mass (w. Standard Armament): | | Mass (w. Standard Armament): | ||
| 25 | | 25 700 kg | ||
|- | |- | ||
| colspan="2" | | | colspan="2" | | ||
|- | |- | ||
| | | Technical Specifications | ||
| | | Advantages | ||
* Wide variety of secondary weapons options | |||
* Excellent hull armour and shielding | |||
* Impressive sensors | |||
* Can dish out as much of a pounding as it takes | |||
<br>Disadvantages | |||
* Low maximum/standard warp speed | |||
* Unwieldy tetryon pulse canon when extended | |||
|- | |- | ||
| Standard Crew Complement: | | Standard Crew Complement: | ||
| | | | ||
* Tactical CONN Pilot (x1) | |||
|- | |- | ||
| | | Warp & Impulse Speeds: | ||
| | | | ||
Warp | * Standard Speed: Warp 5.8 | ||
Warp | * Maximum Speed: Warp 7.6 | ||
* Maximum Cruise: 0.80 C | |||
* Combat Speed: 970 Km/s | |||
|- | |- | ||
| | | Tactical Specs: | ||
| | | | ||
* (x2) Type U+ Pulse Fire Phaser Cannons (forward-facing) | |||
* (x4) Type VI Phaser Arrays (2 forward & 2 aft) | |||
* (x1) Type I Tetryon Pulse Phase Cannon (retracts underneath the hull) | |||
* (x2) Mk II Micro Torpedo Launchers (50-round 30cm Microtorpedoes each) | |||
|- | |- | ||
| | | Defensive Specs: | ||
| | | | ||
* Duranium/Tritanium Composite Hull | |||
* Parametallic Plating | |||
* 11.1cm Type II Ablative Hull Armor (11.5cm OCP) | |||
* Gamma 5/D Class 390 Isoton/s Shields | |||
* Class 3 Structural Integrity Field | |||
* Type XIII Deflector | |||
|- | |- | ||
| | | Engine Specs: | ||
| | | | ||
* Twin-Tandem Quantite Reactor Core | |||
* Wave Drive Propulsion System | |||
* Twin-Tandem ITD-900 Series Class V Impulse Drive | |||
* Pulsed Trentis Mk. IV RCS Thruster Assembly | |||
|- | |||
| Other Systems | |||
| | |||
* Type B Bio-Neural Geldisk FTL Computer Core | |||
* High Data Transfer Speed | |||
* Nano Sub-processor Auxiliary Core | |||
* (x1) Long Range Subspace Antennae | |||
* (x2) Short Range Subspace Antennae | |||
* (x1) Micro Transporter Cluster | |||
* (x1) Short-Range Tractor Beam Emitter | |||
* Standard Environmental System | |||
|- | |- | ||
| | |Sensors | ||
| | | | ||
* Advanced Tactical Sensor Suite | |||
* High Resolution Sensor Range: 18,400,000 Km | |||
* Low Resolution Sensor Range: 36,800,000 Km | |||
* Standard Navigational Sensor Suite | |||
* High Resolution Sensor Range: 5.2 Ly | |||
* Low Resolution Sensor Range: 26.2 Ly | |||
|- | |||
| Other Standard-issue Equipment<br> (stored in cockpit) | |||
| | |||
* Type III Phaser Assault Rifle | |||
* Rations (14 days) | |||
* Power cells (for the pilot's exosuit's hand phaser as well as the rifle stored in the cockpit) | |||
|- | |||
| ''Design:'' | |||
| | |||
''Auctor Lucan'' | |||
|- | |- | ||
| colspan="2" | [[File: | | ''3D Model:'' | ||
| | |||
''Omardex'' & ''Pinarci'' | |||
|- | |||
| colspan="2" | [[File: Ac_409_mk_iii_valkyrie_federation_attack_fighter_by_auctor_lucan-d9fexjn.png |300px]]<br>[[File:Strength-of-the-Pack.png|300px]] | |||
|} | |} | ||
These were the prototype [[warp]] fighters commissioned to the [[USS Theurgy|''USS Theurgy'']] at the end of the 24<sup>th</sup> century. There were originally 16 [[warp]] fighters on the [[USS Theurgy|''Theurgy'']], and they were flown by the Lone-Wolves squadron. | |||
As the war against the [[parasites]] that usurped political power in the [[Federation]] raged, many of the Lone-Wolves were KIA. With the destruction of their fighters, the availability of the Mk III was diminished. This was until the [[USS Theurgy|''Theurgy'']] obtained a few more at the [[Black Opal]] Weapons Facility at the end of March in 2381. | |||
== Fighter Demonstration 01 == | |||
<include iframe src="https://sketchfab.com/models/69578219efe4409e869d9abeb5b01213/embed" width="510" height="380" frameborder="0" scrolling="no" allowfullscreen="allowfullscreen" mozallowfullscreen="true" webkitallowfullscreen="true" onmousewheel="" /> | |||
== Fighter Demonstration 02 == | |||
{{#ev:vimeo|145336203|490}} | |||
== Production History == | |||
[[File:Mk-I-Valkyrie.png|left|200px|thumbnail|''Image: AC-205 Mk I Valkyrie'']]The formation of the [[Starfleet Astronautical Command]] Division was heavily influenced by the successful deployment of ''Peregrine''-class fighters aboard the starships serving as carriers in the fleet. The year 2375 - after the conclusion of the [[Dominion War]] - the [[AC-205 Mk I Valkyrie|AC-205 Mk I Valkyries]] were deployed. These fighters were assigned to the ''[[USS Typhon]]'' (TNG game: Star Trek: Invasion). They were initially designed as a carrier-based fleet engagement craft. The design proved successful, with a high survivability rate matching the heavy fire power available to bring down larger ships. In learning that a full squadron of Valkyries would still require a lot of support from for engagements of a Dominion-War level threat, Starfleet deemed that the attack fighter needed an upgrade (By 2381, the [[AC-205 Mk I Valkyrie|Mk I fighters]] were still being deployed in fairly limited numbers - shuffled around the fleet). | |||
Another development at the time was that a group of influential admirals in the fleet demanded to form a new division that hand-picked the [[Command, Tactical & CONN|Conn]] officers with the most tactical training. It was the only way, they reckoned, to ensure that the fleet used the right kind of pilots for the Valkyrie Program. The original score of 400 personnel - the fleets new Tactical CONN officers - served as the foundation for a new and more organised department for fighter pilots. They accepted only the highest scoring CONN or fight-trained [[Security]] or [[Command, Tactical & CONN|Tactical]] Cadets, and then dealt them another year of training in the fields they lacked from their [[Starfleet Academy|Academy]] training. White became the chosen colour for the [[[[Starfleet Astronautical Command]]]] Division, and the admirals that rode this project into history became the core of the Aerospace Command. | |||
Both the [[AC-205 Mk I Valkyrie|Mk I]] and [[AC-307 Mk II Valkyrie|II]] Valkyries used Rear Intercept Officers (RIOs). The efficiency in which the attack fighters were operated were doubled by allowing the pilots to focus solely on the manoeuvres and weapons employment of the craft during a fight, allowing the RIO to handle comm traffic, emergency repairs and tactic simulations. Among the improvements for the [[AC-307 Mk II Valkyrie|Mk II Valkyrie]] were a new ablative armour compound, improved power plant, and the employment of a hardpoint system beneath the wings. With the Mk II, the Valkyrie truly stepped into a class of her own. | |||
The Mk II's Type U+ cannons worked on the same principles as the Type U on the Defiant-class starships, but at a much smaller scale as well as 20 % reduced output. The first iteration of the U+ could be seen on either side of the [[AC-307 Mk II Valkyrie|MkII]]'s fuselage, but a second version was later made to be wing-mounted on the [[AC-409 Mk III Valkyrie]] (it was the same technology in both versions of the U+ cannons, only on the [[AC-409 Mk III Valkyrie|Mk III]], the entire weapon system was mounted on the wings instead of being inside the fuselage of the fighter (as it is in the [[AC-307 Mk II Valkyrie|Mk II]]). | |||
[[File:Valkyrie-Mk-II-Weapons-Display.png|left|200px|thumbnail|''Image: [[AC-307 Mk II Valkyrie|AC-307 Mk II Valkyrie]]'']]At the success of the [[AC-307 Mk II Valkyrie|Mk II]] and the fleet-wide deployment of the Valkyries in the fleet, [[Starfleet Command]] began looking into the Valkyrie with more interest. So when the project was given new resources, R&D went back to the drawing board to see what could be improved on an already formidable weapon in a MK III version. | |||
The first step was to increase the command, control, and reconnaissance capabilities of the design. Originally, the Valkyrie (both Mk I and Mk II) employed an isolinear twin-core design computer system, with 372 isolinear banks and 106 command pre-processors and data analysis units. This design was quite successful for the use of standard comm traffic control and tactical targeting, but newer sensor package upgrades intended for the Valkyrie were hampered by a core that was already at its limit for processing power. So, with the eagerness of little boys with a new toy to take apart, R&D - under the direct involvement of Director [[Rennan Cooper]] - they began to work on the third iteration of the Valkyrie warp fighter. | |||
By that time, Hyperjet Quantite Mk IV reactor cores were being successfully implemented in the experimental Knight-class Mk I Interceptor. These core types could be sized variably (depending on the design requirements) while still maintaining a very high energy output. A twin-core design was drafted for the new Mk III, and projected numbers suggested the Mk III would see a 25% increase to power output than the Mk I & II series. With this increase in power output, a larger computer core system was designed. Utilizing bio-neural processors and relays, the original frame space needed for the computer systems was reduced and spread out through the center-line of the craft. Computational capacity and storage was increased by another 30%, and a new tactical link-up library software system was implemented. The system provided a clearer and more accurate battlefield image for the pilot, and the integration was so effective that the RIOs were no longer needed - only one pilot was required in the cockpit. | |||
With this new freedom of space within the spacecraft hull, R&D decided a more streamlined hull would benefit the pilot. Their new, sportier look reduced sensor cross-section and improved warp field stability for the twin quantite reactor cores. With the hull redesign came minor changes to weapons load-out: the arrangement of the Type U+ pulse phaser cannons, while the technology was the same as the Mk II, as an upgrade, the warp drive plasma conduit ran through the primary phaser coupling to double the power of the [[AC-409 Mk III Valkyrie|Mk III]]’s phaser cannons. There were pulse or beam firing options available and bolts had a firing rate of 5 per second. The beam setting had lower yield but longer range. The microtorpedo launchers in the Mk II changed only slightly to fit into the new spaceframe. The hard-point system was simplified, and the pulse phaser cell-magazine rack was switched from a vertical feed system to a horizontal feed system – this to combat original design flaws and jams during gravity-inducing combat maneuvers. | |||
[[File:Ride-of-the-Valkyries---Star-Trek-Theurgy.png|left|300px]]Lastly, one more weapon was added: a tetryon pulse phase cannon was installed on the underside of the cockpit within its own hull compartment. This cannon was installed for ground suppression roles, and to give the Valkyrie an added punch in the Space Superiority role. The drawback to the tetryon pulse phase cannon was its limited ammunition and craft maneuverability when utilizing the weapon. Though the weapon itself could effectively neutralize enemy engines and weapons systems, as well as do considerable kinetic energy damage, the weapon itself failed at a remarkable rate when engaged in combat maneuvers. A straight-line course was required for the weapon to work effectively, limiting it to the dangerous Head-to-Head combat maneuvers, and strafing of ground or orbital targets. With these weapon enhancements and increase in power, a slightly larger pair of shield generators were installed, increasing shield sustainable load to 390 isotons/second. It was also given parametallic plating over and the ablative armor was thickened from 10.7 cm to 11.1 cm. | |||
The top speed and warp capabilities of the Mk III remained virtually unchanged, but the increased power output from the new quantite cores benefited the improved avionics, sensor, weapons, and shield systems more than her speed. Despite this, the Valkyrie Mk III could easily go toe-to-toe with the fastest Interceptors currently in service. What she lacked in speed, she made up for in raw firepower. | |||
As of 2381, the Mk III Valkyrie remained a prototype test model, but with the recent development in intergalactic politics and the potential Romulan threat, the project was pushed towards immediate deployment by Aerospace Command. So, since the new ''Theurgy''-class starship - the [[USS Theurgy|''USS Theurgy'']] - was not only being fitted with an A.I. interface, but with a fully operational (if small) fighter assault bay, the decision was made. The Theurgy was given a complement of sixteen Mk III fighters with their own Squadron Commanding Officer and a crew of thirty technicians hailing from Starfleet Operations or Engineering Corps. | |||
The sixteen pilots were named the Lone-Wolves, and though decimated to only twelve pilots after their escape from Earth, the survivors kept fighting to preserve the truth of the corrupted [[Starfleet Command]]. | |||
== | == [[Tactical]] Systems == | ||
[[File:Valkyrie-Weapon-Systems-View.png|right|350px|thumb|''Image: Please see the two options in the bottom right corner.'']]The Mk III Valkyrie had two different hard point configurations, as shown in the image on the right. | |||
Besides the [[Phaser Technology|phasers]], which was a standard technology, other warp fighter tactical systems can be found below: | |||
==== | ==== - Twin Mount Turrets ==== | ||
[[File:Twin-Mounts.png|left|150px]]Twin Dual Cannon guns utilizing an ammunition replicator to create 30 mm Osmiridum shells. These shells were suspended in a small warp field bubble to render them nearly weightless before being electromagnetically propelled at a speed near mach 15 with a rate of up to 1000 rounds per minute, assuming all four cannons were being fired. Devastating against soft targets as well as being effective against armors of nearly all types, it was however, 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 could be 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-409_Mk_III_Valkyrie#M-142_RF_Mass_Driver_Twin_Mount_Turrets|see below for more information]]). | |||
==== | ==== - ECM Pod/ECCM Emitter ==== | ||
[[File:ECM-pod-details.png|left|150px]]Counter measures. These were not options but loaded into the aft of the fuselage as standard. ECM (Electric Counter Measure) was essentially a micro torpedo full of shrapnel and debris with the given craft's transponder signature and sensor reading. It confused the enemy ordinance and caused it to think the cloud of debris was the target. ECCM (Electric Chemical Counter Measure) created a wake similar to a warp, impulse, or thruster engine's wake, fooling such a guided missile into a false lock. | |||
== | ===Launchers=== | ||
[[File: | There were two kinds of launchers that could be mounted underneath the wings of these fighters, one for standard torpedoes and one for micro-torpedoes. | ||
==== - Torpedo Launchers ==== | |||
[[File:TORPEDO LAUNCHER.png|right|150px]]Additional, wing-mounted torpedo launchers that can hold 3 photon torpedoes, EMP torpedoes or Quantum Torpedoes in any kind of combination. It was recommended to mount two of these in order to balance the fighter properly. This meant that the hard-point option of additional torpedo launchers held 6 torpedoes when the Valkyrie was deployed into battle. | |||
==== - External Micro Torpedo Launchers ==== | |||
[[File:torpedo-launcher-details.png|right|150px]]Additional, wing-mounted micro torpedo launchers that can hold either 56 Mk II micro photon torpedoes. It was recommended to mount two of these in order to balance the fighter properly. This meant that the hard-point option of additional micro torpedo launchers held 112 additional micro photon torpedoes in total when the Valkyrie was deployed into battle to complement those that the Valkyrie itself already had as standard internal armament. | |||
===Standard Torpedoes=== | |||
These kinds of torpedoes were loaded into the torpedo launchers. | |||
==== - Mk XXVII Photon Torpedo ==== | |||
[[File:photon-torpedo-details.png|right|150px]]Standard photon torpedo ordinance. The explosion was a matter-antimatter reaction producing large amounts of gamma waves as its primary means of destruction. While smaller in size, and harder to target mid-flight, each torpedo had the approximate yield of 70% compared to the Mk IV (the kind that Federation starships launched from their torpedo bays). This torpedo was deployed in the wing-mounted additional torpedo launchers (see above). | |||
==== - EMP Torpedo ==== | |||
[[File:EMP-torp-details.png|right|150px]]Created the electromagnetic pulse similar to what was created from the high atmosphere detonation of a nuclear warhead. A well-shielded craft would withstand this easily but the weapon would detonate in a burst of broadband, high-intensity electromagnetic energy, capable of disrupting magnetic fields and producing current or voltage surges in conductive materials via magnetic induction. Indirect damage to enemy hardware often proved substantial, and while it had a greater chance of disabling a small craft, the plasma surges could wound or kill soft targets if they were directly exposed. | |||
==== - Mk Q-II Quantum Torpedo ==== | |||
[[File:quantum-torp-details.png|right|150px]]An improvement of the Mk XXV photon torpedo with a higher yield, comparable to that of photon torpedo mounted on Federation Starships. This was a tactical quantum weapon, that utilized a plasma warhead and casings similar in shape to photon torpedoes. The explosion left an antimatter residue and although they were powerful weapons, even a direct hit from a quantum torpedo might not destroy neutronium alloyed targets. | |||
===Hard-Points=== | |||
==== - Mk I Hellbore Torpedo ==== | |||
[[File:hellborne-details.png|right|150px]]An experimental weapon that grew out of historic tandem-charge armour-penetrating designs. Attempting to achieve similar function from contemporary photon and quantum warheads was pointless; the detonation of the first would obliterate the second too early, and a submunition method was less effective than simply firing two torpedoes. Advances in material [[science]] led to a way to produce neutronium in small quantities - fashioned into a penetrator cap and coupled to a small subspace field generator, and driven by a single-burn impulse unit whose size belied its power, the nose of the missile could tear its way through alloys with even the strongest of structural integrity field enhancements, allowing the oversized antimatter warhead in the belly of the torpedo to detonate well inside the defensive screens of its target. Due to the projectile's large size and slower speed compared to the smaller conventional torpedoes, the penetrator cap was ineffective against shielded targets and was best deployed against unprotected hulls. However, the yield was heavy enough to cause severe damage to shields nonetheless. | |||
==== - Mk I Hellhound Cluster Bomb ==== | |||
[[File:hell-hound-details.png|right|150px]]Similar in nature to the photon torpedo, this was a photon torpedo filled with several micro torpedoes. Once the torpedo came in contact with an enemy or a surface, it detonated and fragmented into smaller torpedoes, which spread from the point of impact, also exploding on impact, resulting in a large pattern of torpedo detonations. Deployed correctly, this hard-point had the potential to cause severe damage when scattered upon enemy shields on 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. | |||
== | == 3D Demo: <nowiki>Warp</nowiki> Fighter Weapon Systems == | ||
<include iframe src="https://sketchfab.com/3d-models/starfleet-warp-fighter-weapon-systems-1aa1dce6865b414286c02a7267c4b09e/embed" width="490" height="380" frameborder="0" scrolling="no" allowfullscreen="allowfullscreen" mozallowfullscreen="true" webkitallowfullscreen="true" onmousewheel="" /> | |||
==== | == Type I Tetryon Pulse Phase Cannon == | ||
[[File:Tetryon-Cannon-Details.png|left|400px]] | |||
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. | |||
==== Primary Firing Mode ==== | |||
Once fired, a thin, constant beam of tetryon particles was fired at the target. This stream painted the target for fire, making it easy for further targeting. After painting the target, the [[canon]] made minor adjustments to its aim and fired its primary weapon, a charged pulse [[phaser]] blast. This pulse [[phaser]] blast was stronger than the typical phase bursts from the wing-mounted pulse phasers and was more comparable to the pulse [[phaser]] cannons on a ''Defiant''-class Starship. | |||
A useful benefit to this weapon was how the telemetry data from the tetryon could be linked to other ships in the squadron or with other [[Starfleet]] vessels engaged in a battle. This effectively painted the target for all allied ships in an operation. With that ability, precision targeting by all forces became possible. | |||
Using a squadron of fighters equipped with tetryon canons linked to a heavy weapons emplacement was shown to be an effective defense against cloaked warships. This was because all it took was for one fighter to spot the cloaked vessel by bouncing a tetryon pulse off of it. Once that was done, the signal could be sent to all other fighters and weapons emplacements to fire on the location of the cloaked ship. | |||
==== | ==== Secondary Firing Mode ==== | ||
In this mode, the tetryon cannon fired a concentrated tetryon pulse. The ability of tetryon pulses to cause equipment malfunctions was proven time and again, so it made perfect sense to weaponize this trait. When the concentrated tetryon pulse impacted against a ship’s shields, the tetryon particles tended to weaken the shield bubble, creating a temporary weak point in the shield's systems. This could allow for another ship in formation to fire a more conventional weapon at the weak point, allowing for greater shield penetration than otherwise possible. Often, in order to use this “one-two punch” method of attack, the element leader would be the one using the Tetryon pulse cannon while his wingman followed up with a conventional attack. | |||
While the tetryon Pulse was effective as a means of weakening shields, its greatest asset was revealed when used against a target rendered without shielding. When the particles impacted with a surface, they tended to penetrate through metal surfaces and pass through most armors, affecting whatever computerized systems were in the area near the impact of the pulse. The tetryon particles wreaked havoc on most computer systems, effectively disabling the systems in the affected area. | |||
== | == M-142 RF Mass Driver Twin Mount Turrets == | ||
[[File:Twin-Mounts.png|left|400px]]The M-142 RF Mass Driver Twin Mount was a set of two dual-mass driver semi-automated turrets. These lethal devices were hard-point mounted on the undersides of the impulse drives, and in their default position they faced forward. Aimed similar to the micro-torpedo launchers and pulse [[phaser]] cannons on the Valkyrie, the targeting sensors' arc of fire could track and follow targets in an almost hemispherical firing arc. While the tracking systems were unable to effectively track and hit small agile targets like Shuttles Fighters and small auxiliary craft, it was effective at striking large targets, like starships, and could strike with pinpoint accuracy on stationary or slow moving targets such as Starbases, ground installations, or subsonic moving targets such as ground transports. | |||
The nature of the weapon was less a conventional gun and in fact had far more in common with the tubes used to fire torpedoes on a starship, combined with the warp field bubble projectors used on the Valkyrie itself. By interfacing through the ship's power regulation systems the stardrive of the Valkyrie sent the necessary power to create a warp field bubble within the barrels of the weapon. This short lasting warp field formed around a 30 mm Osmiridium shell created via the weapon systems onboard replicator. Now virtually weightless, even near high G environments like outer atmospheres of Gas giants, the shell was pushed through a magnetic field coil, reaching speeds of Mach 15. Capable of a rate of fire of 250 Rounds per minute per barrel (a little over four rounds per second), with all barrels firing this allowed for a total of 1000 rounds per minute. | |||
Its primary role in combat was not for space superiority (Fighter to fighter) warfare but as a means of aerial or orbital support for ground combatants. It was also quite suitable for pinpoint strikes on starbases or capital ships after their shields had been dealt with. With the correct sensor configurations, this weapon could also target via remote detection of tetryon reflection. This allowed a ground operative with a tetryon targeting based weapon to be used as a remote targeting system. These pulses could then be interpreted as a target by the turrets systems, allowing for ground units to effectively paint targets via tetryon pulse for a precision aerial strike. This added a 4th function to the [[Security#The_Accipiter|Accipiter]] as its tetryon pulse systems could be used as a targeting system for the Twin mounts or any of the Valkyrie's other weapons systems. | |||
====Advantages==== | |||
* Excellent at providing air support for ground [[operations]]. | |||
* High rate of fire. | |||
* Effective against conventional, energy reflecting, or ablative armors. | |||
* Devastatingly effective against soft targets. | |||
* Large targeting arc (360 degree rotational arc covering Forward, Aft, Port, and Starboard) with 15 to 66 degree ventral targeting arc. | |||
* Could be set to fixed forward position. | |||
* Cannons could be set to staggered bursts (4 barrels each fire in a sequence one at a time in a burst of fire) or in a 4 cannon Blast (all 4 fire at once in a single blast) | |||
* When in forward position, it could be potentially devastating against other fighters if their shields had been taken down, providing the pilot could get a solid lock against their target. At close ranges or in atmosphere it could also be an effective close range dog-fighting weapons system similar to the use of guns on a real life jet fighter. | |||
====Disadvantages==== | |||
* Maneuverability is slightly reduced | |||
* These weapons are horribly ineffective against shielded targets. | |||
* The Twin Mounts are rendered completely ineffective if fired in the arc of a ship's deflector array. Attacking the forward of a Starship with them was absolutely useless unless the deflector dish is inoperative. | |||
* If damaged, there could be power loss from the engine systems. | |||
* If severely damaged, there can be small scale localized [[warp]] core breach-like effects. Potentially sufficient to cause catastrophic failure of Impulse and stardrive systems up to and including a full scale [[warp]] core breech. | |||
* The auto targeting systems were unable to effectively track agile small targets effectively. | |||
* Twin Mounts have absolutely no ability to target above the fighter's "Horizon”, meaning there is no dorsal arc of fire. | |||
* To be of use in a dog fighting scenario, the pilot has to be able to fly very well and get a manual target lock without any aiming corrections like with phasers or torpedoes. | |||
====Note==== | |||
In the future that brought the [[USS Calamity|''Calamity'']]-project to life, this system was improved on so heavily that the replicator, power supply, [[warp]] bubble generator, and rail gun firing system were able to be scaled down into a large rifle. The culmination of this research and progress was the [[The_Accipiter|RG-TR1506 Accipiter]]. The [[The_Accipiter|Accipiter]] used a rail gun operation while the Twin Mount's propulsion was a gauss gun based system. | |||
==== | == Ejection Systems == | ||
==== Escape Pod ==== | |||
[[File:Valkyries-Ascending.png|right|320px]] | |||
All Valkyries were equipped with ejection modules or "pods". These allowed for rapid emergency egress from the vehicle in case of danger. Linked to dedicated high speed processors, automatic sensors could detect certain types of danger and initiate an eject sequence automatically. This was especially useful if the pilot had been rendered unconscious through a blackout or other injury and the vehicle was in danger of crashing. | |||
Modules had self-righting mechanisms in their base to ensure a correct orientation during landing. Landing was accomplished by a single use anti-grav module. Free falling until they were 3 meters from the ground, the ejection seat/pod activated the AG module, which burned out as it landed the unit (relatively) gently. The pod remained pressurized with approximately 20 minutes of air, allowing a pilot time to completely seal his suit and activate his personal survival equipment. Once ready, the pilot had the option of discarding the pod by activating a manual release. | |||
=== | ==== ETS (Emergency Transport System) ==== | ||
By the late 24th century, emergency transport was further improved through [[Starfleet]]'s development of a single-person, single-use, one-way emergency transport unit. The device was small enough to be hand-held and could transport to specified coordinates with a single touch. Because of its extreme limitations, this device was not widely deployed and was still considered a prototype in 2379. [see Star Trek: Nemesis] | |||
The Valkyries have built-in Emergency Transport Systems (ETS) in the cockpit - not the small prototype version - designated to the pilot and worn gear alone, with a one-way pre-set location for the ''[[USS Theurgy]]''. The Emergency transporter could be reprogrammed to send the pilot to a new location (chosen by the pilot) because of the possibility of long-range missions, but this system was best utilized in the event of defending the ''[[USS Theurgy|Theurgy]]'' - being within Transporter range. | |||
[[Category:Technical Specifications]] | |||
[[Category:Fighters & Shuttles]] | |||
[[Category:Fighters & Shuttles Specifications]] |
Latest revision as of 06:51, 20 September 2022
Name: | Mk III Valkyrie-class |
Model: | AC-409 |
Starship Type: | Federation Warp Fighter |
Production Status: | Prototype Testing Stage |
Role: |
|
Constructed: | Antares Shipyards |
Commissioned: | October 9th, 2378 Same as the USS Theurgy |
Dimensions: |
|
Mass (w. Standard Armament): | 25 700 kg |
Technical Specifications | Advantages
|
Standard Crew Complement: |
|
Warp & Impulse Speeds: |
|
Tactical Specs: |
|
Defensive Specs: |
|
Engine Specs: |
|
Other Systems |
|
Sensors |
|
Other Standard-issue Equipment (stored in cockpit) |
|
Design: |
Auctor Lucan |
3D Model: |
Omardex & Pinarci |
These were the prototype warp fighters commissioned to the USS Theurgy at the end of the 24th century. There were originally 16 warp fighters on the Theurgy, and they were flown by the Lone-Wolves squadron.
As the war against the parasites that usurped political power in the Federation raged, many of the Lone-Wolves were KIA. With the destruction of their fighters, the availability of the Mk III was diminished. This was until the Theurgy obtained a few more at the Black Opal Weapons Facility at the end of March in 2381.
Fighter Demonstration 01
Fighter Demonstration 02
Production History
The formation of the Starfleet Astronautical Command Division was heavily influenced by the successful deployment of Peregrine-class fighters aboard the starships serving as carriers in the fleet. The year 2375 - after the conclusion of the Dominion War - the AC-205 Mk I Valkyries were deployed. These fighters were assigned to the USS Typhon (TNG game: Star Trek: Invasion). They were initially designed as a carrier-based fleet engagement craft. The design proved successful, with a high survivability rate matching the heavy fire power available to bring down larger ships. In learning that a full squadron of Valkyries would still require a lot of support from for engagements of a Dominion-War level threat, Starfleet deemed that the attack fighter needed an upgrade (By 2381, the Mk I fighters were still being deployed in fairly limited numbers - shuffled around the fleet).
Another development at the time was that a group of influential admirals in the fleet demanded to form a new division that hand-picked the Conn officers with the most tactical training. It was the only way, they reckoned, to ensure that the fleet used the right kind of pilots for the Valkyrie Program. The original score of 400 personnel - the fleets new Tactical CONN officers - served as the foundation for a new and more organised department for fighter pilots. They accepted only the highest scoring CONN or fight-trained Security or Tactical Cadets, and then dealt them another year of training in the fields they lacked from their Academy training. White became the chosen colour for the [[Starfleet Astronautical Command]] Division, and the admirals that rode this project into history became the core of the Aerospace Command.
Both the Mk I and II Valkyries used Rear Intercept Officers (RIOs). The efficiency in which the attack fighters were operated were doubled by allowing the pilots to focus solely on the manoeuvres and weapons employment of the craft during a fight, allowing the RIO to handle comm traffic, emergency repairs and tactic simulations. Among the improvements for the Mk II Valkyrie were a new ablative armour compound, improved power plant, and the employment of a hardpoint system beneath the wings. With the Mk II, the Valkyrie truly stepped into a class of her own.
The Mk II's Type U+ cannons worked on the same principles as the Type U on the Defiant-class starships, but at a much smaller scale as well as 20 % reduced output. The first iteration of the U+ could be seen on either side of the MkII's fuselage, but a second version was later made to be wing-mounted on the AC-409 Mk III Valkyrie (it was the same technology in both versions of the U+ cannons, only on the Mk III, the entire weapon system was mounted on the wings instead of being inside the fuselage of the fighter (as it is in the Mk II).
At the success of the Mk II and the fleet-wide deployment of the Valkyries in the fleet, Starfleet Command began looking into the Valkyrie with more interest. So when the project was given new resources, R&D went back to the drawing board to see what could be improved on an already formidable weapon in a MK III version.
The first step was to increase the command, control, and reconnaissance capabilities of the design. Originally, the Valkyrie (both Mk I and Mk II) employed an isolinear twin-core design computer system, with 372 isolinear banks and 106 command pre-processors and data analysis units. This design was quite successful for the use of standard comm traffic control and tactical targeting, but newer sensor package upgrades intended for the Valkyrie were hampered by a core that was already at its limit for processing power. So, with the eagerness of little boys with a new toy to take apart, R&D - under the direct involvement of Director Rennan Cooper - they began to work on the third iteration of the Valkyrie warp fighter.
By that time, Hyperjet Quantite Mk IV reactor cores were being successfully implemented in the experimental Knight-class Mk I Interceptor. These core types could be sized variably (depending on the design requirements) while still maintaining a very high energy output. A twin-core design was drafted for the new Mk III, and projected numbers suggested the Mk III would see a 25% increase to power output than the Mk I & II series. With this increase in power output, a larger computer core system was designed. Utilizing bio-neural processors and relays, the original frame space needed for the computer systems was reduced and spread out through the center-line of the craft. Computational capacity and storage was increased by another 30%, and a new tactical link-up library software system was implemented. The system provided a clearer and more accurate battlefield image for the pilot, and the integration was so effective that the RIOs were no longer needed - only one pilot was required in the cockpit.
With this new freedom of space within the spacecraft hull, R&D decided a more streamlined hull would benefit the pilot. Their new, sportier look reduced sensor cross-section and improved warp field stability for the twin quantite reactor cores. With the hull redesign came minor changes to weapons load-out: the arrangement of the Type U+ pulse phaser cannons, while the technology was the same as the Mk II, as an upgrade, the warp drive plasma conduit ran through the primary phaser coupling to double the power of the Mk III’s phaser cannons. There were pulse or beam firing options available and bolts had a firing rate of 5 per second. The beam setting had lower yield but longer range. The microtorpedo launchers in the Mk II changed only slightly to fit into the new spaceframe. The hard-point system was simplified, and the pulse phaser cell-magazine rack was switched from a vertical feed system to a horizontal feed system – this to combat original design flaws and jams during gravity-inducing combat maneuvers.
Lastly, one more weapon was added: a tetryon pulse phase cannon was installed on the underside of the cockpit within its own hull compartment. This cannon was installed for ground suppression roles, and to give the Valkyrie an added punch in the Space Superiority role. The drawback to the tetryon pulse phase cannon was its limited ammunition and craft maneuverability when utilizing the weapon. Though the weapon itself could effectively neutralize enemy engines and weapons systems, as well as do considerable kinetic energy damage, the weapon itself failed at a remarkable rate when engaged in combat maneuvers. A straight-line course was required for the weapon to work effectively, limiting it to the dangerous Head-to-Head combat maneuvers, and strafing of ground or orbital targets. With these weapon enhancements and increase in power, a slightly larger pair of shield generators were installed, increasing shield sustainable load to 390 isotons/second. It was also given parametallic plating over and the ablative armor was thickened from 10.7 cm to 11.1 cm.
The top speed and warp capabilities of the Mk III remained virtually unchanged, but the increased power output from the new quantite cores benefited the improved avionics, sensor, weapons, and shield systems more than her speed. Despite this, the Valkyrie Mk III could easily go toe-to-toe with the fastest Interceptors currently in service. What she lacked in speed, she made up for in raw firepower.
As of 2381, the Mk III Valkyrie remained a prototype test model, but with the recent development in intergalactic politics and the potential Romulan threat, the project was pushed towards immediate deployment by Aerospace Command. So, since the new Theurgy-class starship - the USS Theurgy - was not only being fitted with an A.I. interface, but with a fully operational (if small) fighter assault bay, the decision was made. The Theurgy was given a complement of sixteen Mk III fighters with their own Squadron Commanding Officer and a crew of thirty technicians hailing from Starfleet Operations or Engineering Corps.
The sixteen pilots were named the Lone-Wolves, and though decimated to only twelve pilots after their escape from Earth, the survivors kept fighting to preserve the truth of the corrupted Starfleet Command.
Tactical Systems
The Mk III Valkyrie had two different hard point configurations, as shown in the image on the right.
Besides the phasers, which was a standard technology, other warp fighter tactical systems can be found below:
- Twin Mount Turrets
Twin Dual Cannon guns utilizing an ammunition replicator to create 30 mm Osmiridum shells. These shells were suspended in a small warp field bubble to render them nearly weightless before being electromagnetically propelled at a speed near mach 15 with a rate of up to 1000 rounds per minute, assuming all four cannons were being fired. Devastating against soft targets as well as being effective against armors of nearly all types, it was however, 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 could be 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 (see below for more information).
- ECM Pod/ECCM Emitter
Counter measures. These were not options but loaded into the aft of the fuselage as standard. ECM (Electric Counter Measure) was essentially a micro torpedo full of shrapnel and debris with the given craft's transponder signature and sensor reading. It confused the enemy ordinance and caused it to think the cloud of debris was the target. ECCM (Electric Chemical Counter Measure) created a wake similar to a warp, impulse, or thruster engine's wake, fooling such a guided missile into a false lock.
Launchers
There were two kinds of launchers that could be mounted underneath the wings of these fighters, one for standard torpedoes and one for micro-torpedoes.
- Torpedo Launchers
Additional, wing-mounted torpedo launchers that can hold 3 photon torpedoes, EMP torpedoes or Quantum Torpedoes in any kind of combination. It was recommended to mount two of these in order to balance the fighter properly. This meant that the hard-point option of additional torpedo launchers held 6 torpedoes when the Valkyrie was deployed into battle.
- External Micro Torpedo Launchers
Additional, wing-mounted micro torpedo launchers that can hold either 56 Mk II micro photon torpedoes. It was recommended to mount two of these in order to balance the fighter properly. This meant that the hard-point option of additional micro torpedo launchers held 112 additional micro photon torpedoes in total when the Valkyrie was deployed into battle to complement those that the Valkyrie itself already had as standard internal armament.
Standard Torpedoes
These kinds of torpedoes were loaded into the torpedo launchers.
- Mk XXVII Photon Torpedo
Standard photon torpedo ordinance. The explosion was a matter-antimatter reaction producing large amounts of gamma waves as its primary means of destruction. While smaller in size, and harder to target mid-flight, each torpedo had the approximate yield of 70% compared to the Mk IV (the kind that Federation starships launched from their torpedo bays). This torpedo was deployed in the wing-mounted additional torpedo launchers (see above).
- EMP Torpedo
Created the electromagnetic pulse similar to what was created from the high atmosphere detonation of a nuclear warhead. A well-shielded craft would withstand this easily but the weapon would detonate in a burst of broadband, high-intensity electromagnetic energy, capable of disrupting magnetic fields and producing current or voltage surges in conductive materials via magnetic induction. Indirect damage to enemy hardware often proved substantial, and while it had a greater chance of disabling a small craft, the plasma surges could wound or kill soft targets if they were directly exposed.
- Mk Q-II Quantum Torpedo
An improvement of the Mk XXV photon torpedo with a higher yield, comparable to that of photon torpedo mounted on Federation Starships. This was a tactical quantum weapon, that utilized a plasma warhead and casings similar in shape to photon torpedoes. The explosion left an antimatter residue and although they were powerful weapons, even a direct hit from a quantum torpedo might not destroy neutronium alloyed targets.
Hard-Points
- Mk I Hellbore Torpedo
An experimental weapon that grew out of historic tandem-charge armour-penetrating designs. Attempting to achieve similar function from contemporary photon and quantum warheads was pointless; the detonation of the first would obliterate the second too early, and a submunition method was less effective than simply firing two torpedoes. Advances in material science led to a way to produce neutronium in small quantities - fashioned into a penetrator cap and coupled to a small subspace field generator, and driven by a single-burn impulse unit whose size belied its power, the nose of the missile could tear its way through alloys with even the strongest of structural integrity field enhancements, allowing the oversized antimatter warhead in the belly of the torpedo to detonate well inside the defensive screens of its target. Due to the projectile's large size and slower speed compared to the smaller conventional torpedoes, the penetrator cap was ineffective against shielded targets and was best deployed against unprotected hulls. However, the yield was heavy enough to cause severe damage to shields nonetheless.
- Mk I Hellhound Cluster Bomb
Similar in nature to the photon torpedo, this was a photon torpedo filled with several micro torpedoes. Once the torpedo came in contact with an enemy or a surface, it detonated and fragmented into smaller torpedoes, which spread from the point of impact, also exploding on impact, resulting in a large pattern of torpedo detonations. Deployed correctly, this hard-point had the potential to cause severe damage when scattered upon enemy shields on 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.
3D Demo: Warp Fighter Weapon Systems
Type I Tetryon Pulse Phase Cannon
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.
Primary Firing Mode
Once fired, a thin, constant beam of tetryon particles was fired at the target. This stream painted the target for fire, making it easy for further targeting. After painting the target, the canon made minor adjustments to its aim and fired its primary weapon, a charged pulse phaser blast. This pulse phaser blast was stronger than the typical phase bursts from the wing-mounted pulse phasers and was more comparable to the pulse phaser cannons on a Defiant-class Starship.
A useful benefit to this weapon was how the telemetry data from the tetryon could be linked to other ships in the squadron or with other Starfleet vessels engaged in a battle. This effectively painted the target for all allied ships in an operation. With that ability, precision targeting by all forces became possible.
Using a squadron of fighters equipped with tetryon canons linked to a heavy weapons emplacement was shown to be an effective defense against cloaked warships. This was because all it took was for one fighter to spot the cloaked vessel by bouncing a tetryon pulse off of it. Once that was done, the signal could be sent to all other fighters and weapons emplacements to fire on the location of the cloaked ship.
Secondary Firing Mode
In this mode, the tetryon cannon fired a concentrated tetryon pulse. The ability of tetryon pulses to cause equipment malfunctions was proven time and again, so it made perfect sense to weaponize this trait. When the concentrated tetryon pulse impacted against a ship’s shields, the tetryon particles tended to weaken the shield bubble, creating a temporary weak point in the shield's systems. This could allow for another ship in formation to fire a more conventional weapon at the weak point, allowing for greater shield penetration than otherwise possible. Often, in order to use this “one-two punch” method of attack, the element leader would be the one using the Tetryon pulse cannon while his wingman followed up with a conventional attack.
While the tetryon Pulse was effective as a means of weakening shields, its greatest asset was revealed when used against a target rendered without shielding. When the particles impacted with a surface, they tended to penetrate through metal surfaces and pass through most armors, affecting whatever computerized systems were in the area near the impact of the pulse. The tetryon particles wreaked havoc on most computer systems, effectively disabling the systems in the affected area.
M-142 RF Mass Driver Twin Mount Turrets
The M-142 RF Mass Driver Twin Mount was a set of two dual-mass driver semi-automated turrets. These lethal devices were hard-point mounted on the undersides of the impulse drives, and in their default position they faced forward. Aimed similar to the micro-torpedo launchers and pulse phaser cannons on the Valkyrie, the targeting sensors' arc of fire could track and follow targets in an almost hemispherical firing arc. While the tracking systems were unable to effectively track and hit small agile targets like Shuttles Fighters and small auxiliary craft, it was effective at striking large targets, like starships, and could strike with pinpoint accuracy on stationary or slow moving targets such as Starbases, ground installations, or subsonic moving targets such as ground transports.
The nature of the weapon was less a conventional gun and in fact had far more in common with the tubes used to fire torpedoes on a starship, combined with the warp field bubble projectors used on the Valkyrie itself. By interfacing through the ship's power regulation systems the stardrive of the Valkyrie sent the necessary power to create a warp field bubble within the barrels of the weapon. This short lasting warp field formed around a 30 mm Osmiridium shell created via the weapon systems onboard replicator. Now virtually weightless, even near high G environments like outer atmospheres of Gas giants, the shell was pushed through a magnetic field coil, reaching speeds of Mach 15. Capable of a rate of fire of 250 Rounds per minute per barrel (a little over four rounds per second), with all barrels firing this allowed for a total of 1000 rounds per minute.
Its primary role in combat was not for space superiority (Fighter to fighter) warfare but as a means of aerial or orbital support for ground combatants. It was also quite suitable for pinpoint strikes on starbases or capital ships after their shields had been dealt with. With the correct sensor configurations, this weapon could also target via remote detection of tetryon reflection. This allowed a ground operative with a tetryon targeting based weapon to be used as a remote targeting system. These pulses could then be interpreted as a target by the turrets systems, allowing for ground units to effectively paint targets via tetryon pulse for a precision aerial strike. This added a 4th function to the Accipiter as its tetryon pulse systems could be used as a targeting system for the Twin mounts or any of the Valkyrie's other weapons systems.
Advantages
- Excellent at providing air support for ground operations.
- High rate of fire.
- Effective against conventional, energy reflecting, or ablative armors.
- Devastatingly effective against soft targets.
- Large targeting arc (360 degree rotational arc covering Forward, Aft, Port, and Starboard) with 15 to 66 degree ventral targeting arc.
- Could be set to fixed forward position.
- Cannons could be set to staggered bursts (4 barrels each fire in a sequence one at a time in a burst of fire) or in a 4 cannon Blast (all 4 fire at once in a single blast)
- When in forward position, it could be potentially devastating against other fighters if their shields had been taken down, providing the pilot could get a solid lock against their target. At close ranges or in atmosphere it could also be an effective close range dog-fighting weapons system similar to the use of guns on a real life jet fighter.
Disadvantages
- Maneuverability is slightly reduced
- These weapons are horribly ineffective against shielded targets.
- The Twin Mounts are rendered completely ineffective if fired in the arc of a ship's deflector array. Attacking the forward of a Starship with them was absolutely useless unless the deflector dish is inoperative.
- If damaged, there could be power loss from the engine systems.
- If severely damaged, there can be small scale localized warp core breach-like effects. Potentially sufficient to cause catastrophic failure of Impulse and stardrive systems up to and including a full scale warp core breech.
- The auto targeting systems were unable to effectively track agile small targets effectively.
- Twin Mounts have absolutely no ability to target above the fighter's "Horizon”, meaning there is no dorsal arc of fire.
- To be of use in a dog fighting scenario, the pilot has to be able to fly very well and get a manual target lock without any aiming corrections like with phasers or torpedoes.
Note
In the future that brought the Calamity-project to life, this system was improved on so heavily that the replicator, power supply, warp bubble generator, and rail gun firing system were able to be scaled down into a large rifle. The culmination of this research and progress was the RG-TR1506 Accipiter. The Accipiter used a rail gun operation while the Twin Mount's propulsion was a gauss gun based system.
Ejection Systems
Escape Pod
All Valkyries were equipped with ejection modules or "pods". These allowed for rapid emergency egress from the vehicle in case of danger. Linked to dedicated high speed processors, automatic sensors could detect certain types of danger and initiate an eject sequence automatically. This was especially useful if the pilot had been rendered unconscious through a blackout or other injury and the vehicle was in danger of crashing.
Modules had self-righting mechanisms in their base to ensure a correct orientation during landing. Landing was accomplished by a single use anti-grav module. Free falling until they were 3 meters from the ground, the ejection seat/pod activated the AG module, which burned out as it landed the unit (relatively) gently. The pod remained pressurized with approximately 20 minutes of air, allowing a pilot time to completely seal his suit and activate his personal survival equipment. Once ready, the pilot had the option of discarding the pod by activating a manual release.
ETS (Emergency Transport System)
By the late 24th century, emergency transport was further improved through Starfleet's development of a single-person, single-use, one-way emergency transport unit. The device was small enough to be hand-held and could transport to specified coordinates with a single touch. Because of its extreme limitations, this device was not widely deployed and was still considered a prototype in 2379. [see Star Trek: Nemesis]
The Valkyries have built-in Emergency Transport Systems (ETS) in the cockpit - not the small prototype version - designated to the pilot and worn gear alone, with a one-way pre-set location for the USS Theurgy. The Emergency transporter could be reprogrammed to send the pilot to a new location (chosen by the pilot) because of the possibility of long-range missions, but this system was best utilized in the event of defending the Theurgy - being within Transporter range.