Tactical CONN
From Star Trek: Theurgy Wiki
The Tactical CONN department was where the Starfleet fighter pilots belonged, where space aviation and military/tactical knowledge went hand in hand. They worked very closely with both the CONN and Tactical departments and the department color was white.
Background Information: Tactical CONN
The formation of the Starfleet Aerospace Command in 2375 was heavily influenced by the successful deployment of Peregrine-class fighters aboard the starships serving as carriers in the fleet, yet the USS Theurgy did not hold a squadron of Peregrine-class fighters aboard, but the more developed Valkyrie-class. Namely, the prototype Mk III version, a superior fighter that made use of recent advances in technology.
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. Initially, 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 for engagements of a Dominion-War level threat, Starfleet deemed that the attack fighter needed an upgrade. By 2381, these 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 department 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 these fighters. The original score of 400 personnel - the fleets new Tactical CONN officers - served as the foundation for a new and more organized 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 color for the department, 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 maneuvers 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 armor 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. 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. Initially, they had considered Tactical CONN another spear in Starfleet's arsenal. So when the project was given new funding, R&D went back to the drawing board to see what could be improved on an already formidable weapon.
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 preprocessors 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 began a computer system redesign from the ground up, which would lead to hull, engine, and weapons redesign, and end in an almost completely new Space Superiority attack fighter: the AC-409 Mk III Valkyrie.
By that time, Hyperjet Quantite Mk IV reactor cores were being successfully implemented in the experimental Knight-class 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 not needed any more - 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 standard Type-XII pulse phaser cannons and 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 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 engine 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 maneuver, 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. The ablative armor was also 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. inter-phase, 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 original pilots on the Theurgy were named the Lone Wolves, decimated to only twelve pilots after their escape from Earth. In March of 2381 - as of the Battle of Starbase 84 - there were only four of the original pilots left, but twelve fighter pilots defected to the Theurgy during the battle, forming the new squadron with the same name.
Tactical CONN Positions
Tactical CONN were trained in aerodynamics, support craft, fighter engines, flight systems, meteorology, and navigation, as well as flight rules and regulations. They also received training in maintenance and supervision of ground crew personnel. They were trained in combat fighter tactics in space as well as atmospheres. They all began training with runabouts, shuttles, and transports so were qualified on all types before graduation.
| Tactical CONN Roles | |
|---|---|
| Role | Description |
| Group Commander [CAG] [N/A For Playing] |
The Group Commander was in charge of all things related to his Group's Tactical CONN personnel and their fighters, generally a responsibility of all Flight Wings assigned to a base or starship. The CAG was responsible for all the personnel assigned to the Group on the ship/facility, and ensuring that combat readiness, mission load outs, maintenance checks, and repairs were done so all fighters were mission ready. The CAG reported to the Commanding Officer or Executive Officer and was a member of the Senior Staff. |
| Wing Commander [N/A For Playing] |
The Wing Commander was in charge of all things related to his Wing's fighters, generally a responsibility of over 30 attack fighters. As well, the Wing Commander was responsible for all the personnel assigned to the Wing on the ship/facility, and ensuring that combat readiness, mission specific load-outs, maintenance, and repairs were completed maximizing readiness. If more than 16 fighters were assigned to a ship, it could have had a Wing Commander. If the Wing Commander was the senior Tactical CONN officer assigned to the facility, starbase, or starship, they reported to the Commanding Officer or Executive Officer and were a member of the Senior Staff. |
| Squadron Commanding Officer [SCO] / Squad Leader [Informal Title] |
This was the highest ranking rank on board the USS Theurgy. The SCO was in charge of all things related to his Squadron's fighters, generally a responsibility for 8 to 24 attack fighters (2 to 4 Flights). The SCO was responsible for all the Tactical CONN personnel assigned to the Squadron on the ship/facility, and ensuring the combat readiness, correct mission specific load outs, maintenance checks, and repairs were done so all fighters were mission ready. A SCO reported to the CAG or Wing Commander. If the SCO was the senior Tactical CONN officer assigned to the starship, starbase, or facility they reported to the Commanding Officer or Executive Officer and were a member of the Senior Staff. |
| Flight Leader |
The Flight Leader was in charge of all things related to his Flight's fighters, responsible for 4 to 8 attack fighters. The Flight Leader was also responsible for all the Tactical CONN personnel assigned to the flight, ensuring that all his fighters were combat ready, supervising maintenance and repairs on the Flight's attack fighters. The Flight Leaders reported to the SCO of their Squadron. |
| Element Leader |
The Element Leader was the Tactical leader of a pair of attack fighters. An Element was the smallest unit used by Tactical Conn. Only on rare or desperate times would a pilot and his/her attack fighter be deployed as a lone craft. The Element Leader reported directly to the Flight Leader. |
| Rear Intercept Officer |
The Rear Intercept Officer (RIO) sits behind the pilot and manages the battlefield and mission execution. Unlike pilots who are usually commissioned officers, the RIO is normally a non commissioned officer.
Tasks of an RIO:
The RIO has access to the ship's controls only in case of emergency. While his basic training includes pilot training on small spacecraft and he is able to pilot and land a spaceship if needed, he does not have the experience with hands on flying like pilots do. His advanced training focuses more on mission planning, battlefield management, navigation and communication skills. His job is to make sure the mission is executed as planned and that the pilot can fulfill his tasks. Crew coordination between pilot and RIO is the most important factor to spaceship efficiency. When engaging in BVR (Beyond Visual Range) combat, the RIO is thinking offensively, while the pilot is mainly defensively minded. As soon as the engagement enters the visual realm, the pilot will switch to an offensive mindset, while the RIO will take over the task to defend the spaceship with countermeasures and visual lookout. |
Tactical CONN Exosuit
The Mk II Tactical CONN-class exosuit was a low-profile EVA suit with adjustable-size exoskeletal limb and torso capabilities resultant from small overlapping sectional side plating, which dynamically expanded and contracted the overlap distance of its many outer plates, adapting to the wearer's limb length and girth. The plates also offered a varying degree of flexibility for its wearers, having moved in conjunction with body movements during general use.
The Mk II designs were composed of four layers: closest to the skin was a liquid heat insulation layer, next a pressure-restraint layer, then a micrometeoroid resistant layer which was reinforced with lightweight ablative ceramic sheeting, and lastly additional sectional dura-ceramic ablative armor plating for improved armor capacity. The role of the liquid head insulation later was to keep the wearer's body at a preferred/comfortable temperature. The pressure-restraint layer maintained appropriate internal air-pressure, and was intended to prevent atmosphere from escaping the suit; however, unlike the Security-class exosuit, it provided a significantly higher level of constriction capability, which was a requirement to more effectively serve as a G-Suit. This meant that though better suited to a Pilot's G-Force resistance needs, the Tactical CONN-class exosuits were somewhat grander in overall mass and volume of the suit, slightly decreasing the design's overall flexibility. The primary outside layer protected its wearer from the extreme temperature changes one might experience in the multitude of environments that exist, cosmic dust particulates, and to a certain extent energy and projectile weapons fire. The final sectional layer covered more common vital-organ locations around the wearer's body and provided a more substantial capacity for weapons damage.
Interwoven into the structure of these exosuits was a synthetic muscular servomechanism and spinal stabilizer column. At the back of the exosuit were the primary pair of low-energy thrusters, which were designed for extended capacity. Additional low-energy thrusters were located in the magnetized hard-shell boots. Yet more small reaction-control thrusters were located throughout key-points of the design as well, allowing for a greater range of dexterous movement. The PM-1 locator beacon on the helmet was fitted with a xenon strobe, capable of generating 9,600 lumens for the sake of visibility during rescue operations. In Mk II designs, stand-alone life support systems would have provided a wearer with oxygen for sixteen-hours instead of the twelve-hour capacity of the previous Mk I design. However, the exosuits were also outfitted with auxiliary oxygen support systems as a back-up to the primary system, offering an additional ten-hours of breathable atmosphere. Lastly, an emergency battery powered a O2 analyzer and carbon-dioxide scrubber could provide up to four-hours of a supply. All-in-all, the total life-support capacity of the Mk II exosuit measured in at around thirty-hours, a whole ten-hours longer than previous designs.
Utility compartments located at the hips and on the outer-sides of the legs often contained the following items:
- Magnetic-retaining thigh holster and ammunition container for Type-II Pulse Phaser Pistol and four additional power cells.
- Hard-shell resealable containers for various items; Type-III Pulse Phaser Rifle power cells, flex-restraints, and other essential gear.
- 20cm retractable parsteel combat/utility knife
Forearm PADDs
Whereas the PADD display read-out of the Mk I design of exosuit was a simplified version of the standard-issue Starfleet variety, the Mk II, and more specifically the Mk II designs employed aboard the USS Theurgy were slightly more complex. Melded with a degree of Savi technology as part of their exchange, these PADDs had granted a broader capacity for sensor-dampening, rendering its wearer near-undetectable by traditional and even some advanced sensor sweeps. Both PADDs were integrated into their respective forearms, and were used to a varying effect; generally however, the left-forearm PADD was programmed to display primary suit interface, recording critical navigational instructions, mission updates, communication code frequencies, and other pieces of vital information. During operations, a dedicated circuit could also record the wearer's biological data and serve to provide rapid diagnosis of injury. The right-forearm PADD was generally programmed to connect with a wearer's weapon read-out interface, allowing for better tactical awareness of the weapons' power-level, as well as easier re-modulation of weapon phase harmonics. Both also served as standard issue tricorders.
In the event that the exosuit's wearer was incapacitated, both PADDs could flash-erase all stored information to prevent it from being compromised, sparing only biomedical subsystems; alternatively, the wearer could deliberately initiate this security measure with a simple encoded voice command via his helmet.
Through-Visor Display [TVD]
Critical flight data: course, speed, sensor readings and the like were displayed for Tactical CONN-class exosuit wearers via their helmet visors. This look-through display was known as TVD, or Through-Visor-Display. The TVD was extremely useful as it allowed a pilot to maintain focus on flight control, while still being situationally aware of their combat environment. Unlike standard Heads-up-Display, which was projected only on the forward canopy, TVD could be observed no matter the direction of the wearers vision, allowing information to remain displayed and updated based on that orientation. Additionally, TVD allowed the wearer to observe through their craft in any direction, via advanced sensor suite and holoprojection within the visor. In practical terms, this allowed a pilot to virtually see through his craft in any direction, and visually scan his surroundings for targets and threats that were not immediately within direct line of sight of the cockpit canopy.
TVD also offered a variety of viewing modes for each crew-member of a craft, and the particular mode which was necessitated could be selected via flight-stick control, or from one of the two PADDs attached to the exosuit. Computer systems would narrow the range of modes available based on the particular environment, and situation the wearer found themselves in. For instance, during space flight, atmospheric landing modes generally not available, and vice versa, unless there were certain criteria met that unlocked them. This lock-out could of course be overridden by the exosuit wearer if the situation dictated it.
Cockpit Gear
- Type III phaser rifle
- Standard combat ration pack (14 days)
- Standard combat medical kit
- Knife with retractable parsteel blade
- 1 field communicator
- Emergency inflatable shelter (1 person)
- 2 half-liter pouches of drinking water
Exosuit Demonstration
The Fighter Assault Bay / Fighter Bay (Informal Term)
Here is the floor plan of the Fighter Assault Bay (more commonly called the Flight Hangar, the Fighter bay, the Hangar etc.) in which the Tactical CONN squadron of AC-409 Mk III Valkyries and AC-477 Mk I Valravns were housed and where the Theurgy’s fighter pilots usually hung out.
Port Side
- Port Flight Ops Both
- Reports to Mission Ops on the Main Bridge
- Port Turbolift Access
- Squadron Commander & Chief of the Deck Office
- Squadron & Fighter Bay Ops Briefing Room
- Communal Squadron Locker Room
- Fighter Bay Gymnasium
- Squadron Mess Hall/Lounge “The Den”
- Head
- Port Jefferies Tubes Access
- Maintenance Bay 1
Starboard Side
- Starboard Flight Ops Both
- Reports to Mission Ops on the Main Bridge
- Starboard Turbolift Access
- Fighter Bay Operations Office
- Used as needed by:
- The Head of Weapons Maintenance & Armaments
- The Head of Fighter Propulsion
- The Head of Avionics, Sensors & Computer Systems
- The Head of Spaceframe & Structure
- Used as needed by:
- Assembly Room (Workshop)
- With Industrial Replicatior & Cargo Transporter
- Armoury
- Hard Point Magazine & Cargo Transporter (for restocking)
- Deck Crew Locker Room
- Deck Crew Mess/Lounge
- Head
- StarboardJefferies Tubes Access
- Maintenance Bay 2
Squadron Spirit
A Tactical CONN pilot was defined by a certain amount of self-confidence and self-respect for their own skills in regards to their training. Some pilots might have been mice outside of the cockpit, but because of training or inner strength, they turned into formidable piloting machines once they got into their Valkyries. The ones that withered under battle pressure were weeded out early in Tactical CONN Academy.
There was also the great trust they had in their fellow pilots; a 'pack' mentality that kicked in. On duty - especially in combat situations - more than half of their fighting ability came from the support provided by their Squadron. Off duty, there was a certain appreciation for the essence of life itself; a certain flare of enjoying life with more color and enthusiasm than necessarily their fellow Starfleet officers might. Day in and day out they would go out there and willingly throw themselves in front of bullets.
Tactical CONN courted death and faced losing friends every day, so there was a constant state of heightened adrenaline, and thus a greater appreciation for life. Their pack mentality generated some off duty tendencies as well, like wearing matching flight jackets, necklaces, or hoodies that bolstered their team spirit.
Common Terminology
Combat Geometry
- Angle Off - The difference between your heading and the ship you wished to attack in degrees
- Angle off Tail (AoT) - The angle between your flight path and the flight path of the ship you wished to attack
- Aspect Angle - The number of degrees between the tail of the other ship and your ship
- Range - The distance between your ship and the target ship
Attack Terms
- Closure Rate - The speed of your ship relative to the speed of the target ship.
- Cone of vulnerability - The area of space that put you in range of your enemy's weapons. The only cone worse than the "Cone of Silence".
- Corner speed - The speed at which a fighter/vessel could achieve its best turn radius
- Turn rate/ Turn radius - The number of degrees a fighter/vessel could pivot per second.
- Weapons Envelope - The area in which a weapon was effective. It was specific to the weapon and included maximum and minimum range.
Types of Pursuit
- Lag pursuit - The opposite of lead pursuit. You made a wider turn instead of a sharper one to a point just behind the tail of the target pursuit.
- Lead pursuit - Taking the path based on your prediction of the flight path of your target. You anticipated where it would be and altered your course to cross the target's flight path. Smaller or more maneuverable craft could get an advantage by taking sharper turns.
- Pure pursuit - Following closely the path of the target.This was the position you wanted to be in for torpedo and missile firing. Good also for closer range with phasers.
Pilot Chatter
- Bandit - Enemy vessel
- Bent - Sensors inoperative
- Bogey - Unknown vessel
- Buddy spike - Being tracked/targeted by friendly forces. Look out for friendly fire
- Bug out - Disengage
- Clean - No contacts
- Clear - No enemy threat to you
- Contact - Located target
- Mud spike - Being targeted by ground radar
- No Joy - No contact of target. Opposite of "tally"
- Target - That thing you are looking for or want to get rid of
- Tally - Opposite of "no joy". Target, bandit, or bogey has been sighted
Formation Flying
- Echelon Formation - Arrow head formation. Flight leader was the point of the arrow.
- Diamond Formation - Similar to above but there was a fighter directly behind the leader at the end to make a diamond shape.
- Line Astern Formation - Flight leader was in the front with the others behind at equal spacing intervals. Think of it as a column.
- Line Abreast Formation - Similar to "line astern" but fighters were arranged like a row. The flight leader was to the extreme left followed by the rest to his/her/its right.
Attack and Defensive Patterns
The patterns described on this page - Attack Patterns - could also effectively be used when writing aerospace combat with a smaller Federation Warp Fighter. A recommendation was to write out the description of the specified maneuvres in some way so that the reader does not have to return here to check what actually happened in the post he/she was reading.
Squadron Organizational Charts
Tactical CONN was comprised of Air Groups, which held four Wings, and in each Wing, there were usually four squadrons. Air Groups served as planetary or starbase defence complements, with the high number of fighters suitable for the defence of large population nodes in the Federation. When commissioned to starships, the fighter complement was usually a single Wing or a couple of squadrons. Depending on the ship's class, a round saucer granted a more capacious Fighter Assault Bay, yet single-squadron fighter complements could be found on other starships that had either been retro-fitted as carriers or built with hangars within the engineering sections.
These single squadrons deployed alone from starships all had in common that they had a wolven theme to their names, since they operated in packs without the support from an entire Wing or Air Group. They could have squadron names like the Lone Wolves on the USS Theurgy, the Grey Wolves on the USS Resolve or the White Wolves on the USS Orcus.
See below for squadron organisational charts for known vessels in Star Trek: Theurgy. Since all fighter pilots at Starbase 84 were NPCs, they can be found on this page: The 23rd Tactical CONN Air Group at Starbase 84
The Lone Wolves Squadron
After the defeat the USS Theurgy at the Battle of Starbase 84, a lot of Tactical CONN Officers were killed, and even more defected to the Theurgy from both the USS Resolve and the USS Orcus. After the loss of Miles Renard, callsign "Iron-Fox", the Squadron Commanding Officer on the Theurgy since the Niga Incident, Captain Ives ordered the formation of a new wolf pack, consisting of Tactical CONN officers from all three ships. The Theurgy's new fighter squadron was still dubbed the Lone Wolves Squadron. A couple of days later, the Lone Wolves fought the Savi in the Azure Nebula. With their numbers so low, they had to arrange their Flights by three, with one Flight leader and 1-2 Fighter pilots.
Interregnum 01-02 (Season 2)
See below for the status of the Lone Wolves Squadron after the conclusion of Advent of War (Episode 01 of Season 2):
| LONE WOLVES SQUADRON - INTERREGNUM 01-02 x11 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x4 AC-477 Mk I Valravns (+1 in storage) | |||
 Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Fighter Pilot Lt. JG Evelyn Rawley ♀ (Human) |
Element Leader Lt. JG Tessa May Lance ♀ (Human) |
Fighter Pilot [VACANCY] ♀/♂ ([Insert Species]) |
 Flight Leader Lt. Daniel Havenborn ♂ (Human) |
Fighter Pilot |
Element Leader Lt. JG Donna Petterson ♀ (Human) |
Fighter Pilot [VACANCY] ♀/♂ ([Insert Species]) |
Flight leader Lt. JG Callax Valin ♂ (Ardanan) |
Fighter Pilot |
Element Leader Ens. Victor vanVinter ♂ (Human) |
Fighter Pilot [VACANCY] ♀/♂ ([Insert Species]) |
 Flight Leader Lt. Regiene Suder ♀ (Betazoid) |
Fighter Pilot Lt. JG Logan Hale ♂ (Human) |
Element Leader Lt. JG Sorek Morgan ♂ (Human/Romulan) |
Fighter Pilot [VACANCY] ♀/♂ ([Insert Species]) |
Advent of War (Episode 01 of Season 2)
See below for the status of the Lone Wolves Squadron when Season 2 began:
| LONE WOLVES SQUADRON - SEASON 02 STARTING x11 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x4 AC-477 Mk I Valravns (+1 in storage) | |||
Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Wolf-02 Fighter Pilot Lt. JG Logan Hale ♂ (Human) | ||
Flight Leader Lt. Cmdr. Miles Renard ♂ (Vulpinian) |
Fighter Pilot Lt. JG Tessa May Lance ♀ (Human) | ||
Wolf-05 Flight Leader Lt. Daniel Havenborn ♂ (Human) |
Fighter Pilot | ||
Flight Leader CWO1 Liliana Walton ♀ (Human) |
Fighter Pilot Lt. JG Alessia Garcia ♀ (Human) |
Fighter Pilot Lt. JG Devyrie Okhala ♀ (Human/Romulan) | |
| ALLEGIANT ESCORT AWAY MISSION | |||
Flight Leader Lt. JG Evelyn Rawley ♀ (Human) |
Fighter Pilot Ens. Isel Nix ♀ (Vulpinian) |
Element Leader Lt. JG Donna Petterson ♀ (Human) |
Fighter Pilot Ens. Nathaniel Isley ♂ (Romulan) |
Aldea Prime Anthology
See below for the status of the Lone Wolves Squadron between Seasons 1 and 2.
| LONE WOLVES SQUADRON - ALDEA PRIME ANTHOLOGY x11 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x4 AC-477 Mk I Valravns | |||
Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Fighter Pilot Lt. JG Evelyn Rawley ♀ (Human) |
Element Leader Lt. JG Donna Petterson ♀ (Human) |
Fighter Pilot |
Flight Leader Lt. Cmdr. Miles Renard ♂ (Vulpinian) |
Fighter Pilot Ens. Nathaniel Isley ♂ (Romulan) |
Element Leader Lt. JG Tessa May Lance ♀ (Human) |
Fighter Pilot Lt. JG Khorin Douglas ♂ (Klingon) |
Wolf-09 Flight Leader Lt. Daniel Havenborn ♂ (Human) |
Fighter Pilot |
Element Leader Ens. Krystal Tancredi ♀ (Human) |
Wolf-12 Fighter Pilot PO3 Lillee t'Jellaieu ♀ (Romulan) |
Flight Leader CWO3 Liliana Walton ♀ (Human) |
Fighter Pilot Lt. JG Alessia Garcia ♀ (Human) |
Element Leader Lt. JG Devyrie Okhala ♀ (Human/Romulan) |
Wolf-16 Fighter Pilot Lt. JG Logan Hale ♂ (Human) |
The Battle of the Apertures
See below for the status of the Lone Wolves Squadron after at the end of Episode 05, Part 2, in the final chapter:
| LONE WOLVES SQUADRON - EP05, IN THE FINAL CHAPTER x6 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x5 AC-477 Mk I Valravns | |||
Wolf-01 - Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Wolf-02 - Fighter Pilot Lt. JG Evelyn Rawley ♀ (Human) |
Lt. JG Donna Petterson ♀ (Human) |
|
Wolf-05 - Flight Leader Lt. Daniel Havenborn ♂ (Human) Callsign: Salvo |
Wolf-06 Fighter Pilot Lt. JG Alessia Garcia ♀ (Human) |
Wolf-07 - Element Leader Lt. JG Tessa May Lance ♀ (Human) |
Wolf-08 - Fighter Pilot PO3 Lillee t'Jellaieu ♀ (Romulan) |
Wolf-09 Flight Leader CWO3 Liliana Walton ♀ (Human) |
Wolf-10 Fighter Pilot Lt. JG Sephiria Arn ♀ (Trill) |
Wolf-11 Element Leader Lt. JG Logan Hale ♂ (Human) |
Wolf-12 Fighter Pilot Lt. JG Jhozahosh sh'Avhennes ♀ (Andorian) |
The Martok Encounter
See below for the status of the Lone Wolves Squadron after it had fought the Savi the first time, and fought the Rotarran:
| LONE WOLVES SQUADRON - EP05, IN CHAPTERS "CHARADES" & "VANTAGE POINTS" x5 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x5 AC-477 Mk I Valravns | |||
Wolf-01 - Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Wolf-02 - Fighter Pilot Lt. JG Evelyn Rawley ♀ (Human) |
Wolf-03 - Fighter Pilot Lt. JG Tessa May Lance ♀ (Human) | |
Wolf-04 - Flight Leader Lt. Daniel Havenborn ♂ (Human) Callsign: Salvo |
Wolf-05 Fighter Pilot Ens. Krystal Tancredi ♀ (Human) |
Destroyed Wolf-06 Fighter Pilot Ens. CJ Slayton ♂ (Human) | |
Destroyed Wolf-07 Flight Leader Lt. Talidenai zh'Idenna ♀ (Andorian) |
Destroyed Wolf-08 Fighter Pilot Lt. JG T'Zantha ♀ (Vulcan) |
Destroyed Wolf-09 Fighter Pilot Lt. JG Cameron Ward ♂ (Human) | |
Wolf-10 Flight Leader Lt. JG Alessia Garcia ♀ (Human) |
Destroyed Wolf-11 Fighter Pilot CPO Chatrine Palm ♀ (Human) | ||
The Battle with the Savi
See below for the status of the Lone Wolves Squadron when battling the Versant the first time:
| LONE WOLVES SQUADRON - BATTLE WITH THE VERSANT EP05 CH01 x7 AC-409 MK III Valkries, x1 AC-307 Mk II Valkyries & x8 AC-477 Mk I Valravns | |||
Wolf-01 - Wolf Leader/SCO Lt Cmdr. Thomas Ravon ♂ (Human) |
Missing-in-Action Wolf-02 - Fighter Pilot Lt. JG Khorin Douglas ♂ (Human/Klingon) |
Wolf-03 - Element Leader Lt. JG Tessa May Lance ♀ (Human) |
Missing-in-Action Wolf-04 - Fighter Pilot Ens. Nathaniel Isley ♂ (Human/Romulan) |
| Wolf-05 - Flight Leader Lt. Daniel Havenborn ♂ (Human) Callsign: Salvo |
Missing-in-Action Wolf-06 Fighter Pilot Ens. K'Ren ♀ (Caitian/Human) |
Wolf-07 Element Leader Ens. Krystal Tancredi ♀ (Human) |
Wolf-08 Fighter Pilot Ens. CJ Slayton ♂ (Human) |
| Wolf-09 Flight Leader Lt. Talidenai zh'Idenna ♀ (Andorian) |
Wolf-10 Fighter Pilot Lt. JG T'Zantha ♀ (Vulcan) |
Destroyed Wolf-11 Element Leader Lt. JG Devyrie Okhala ♀ (Human/Romulan) - MIA |
Destroyed Wolf-12 Fighter Pilot Ens. Esa Ojanpera ♂ (Bajoran) |
| Wolf-13 Flight Leader Lt. JG Alessia Garcia ♀ (Human) |
Destroyed Wolf-14 Fighter Pilot Ens. Minjae Soh ♂ (Human) |
Wolf-15 Element Leader Lt. JG Cameron Ward ♂ (Human) |
Wolf-16 Fighter Pilot CPO Chatrine Palm ♀ (Human) |
The Battle of Starbase 84
Before the USS Theurgy's crew were named outlaws and persecuted across the Alpha Quadrant, the Lone Wolves Squadron consisted of sixteen fighter pilots and just as many Mk III Valkyries. After the Battle of Starbase 84, the squadron has been altered to accept new Tacitcal CONN Officers from other ships. See below for the status of the Lone Wolves at the end of the Battle of Starbase 84, before these additional officers:
| THE FORMER LONE WOLVES SQUADRON (AT THE BATTLE OF STARBASE 84) AC-409 Mk III Valkyries | |||
Missing-in-Action Wolf-01 - Wolf Leader/SCO Lt. Cmdr. Miles Renard ♂ (Vulpinian) |
Destroyed Wolf-02 - Fighter Pilot Ens. Kanti MacTavish ♀ (Trill) | ||
Destroyed Wolf-03 - Flight Leader |
Wolf-04 - Fighter Pilot Ens. CJ Slayton ♂ (Human) |
Destroyed Wolf-05 - Element Leader Ens. Gregor Strand ♂ (Human) |
Destroyed Wolf-06 - Fighter Pilot CPO Carolina Archer ♀ (Human) Callsign: Game |
Destroyed, ETSed Wolf-07 - Flight Leader Lt. JG Tessa May Lance ♀ (Human) |
Destroyed Wolf-08 - Fighter Pilot CPO Earl Lundh ♂ (Human) |
Wolf-09 - Element Leader Lt. JG Evelyn Rawley ♀ (Human) |
Destroyed Wolf-10 - Fighter Pilot Ens. Quint Birch ♂ (Human) |
| Wolf-XX - Former Flight Leader Lt. Thomas Ravon ♂ (Human) | |||
The Black Wolves Squadron
At the Battle of Starbase 84, eight Valravn fighters in the White Wolves Squadron defected to the USS Theurgy, being integrated into the Lone Wolves Squadron. The rest stayed loyal to the Commanding Officer of the USS Orcus. Yet since they were so few in numbers after the battle, they were integrated into the Black Wolves Squadron aboard the USS Dauntless.
See below for the status of the Black Wolves when Task Force Archeron intercepted Vector 03 of the USS Theurgy in Episode 05:
| BLACK WOLVES SQUADRON - EP05, IN CHAPTERS "VERTEX" & "KNIFE'S EDGE" x10 AC-307 Mk II Valkyries & x6 AC-477 Mk I Valravns | |||
Destroyed Wolf-01 - Wolf Leader Lt Cmdr. Ash Bates ♂ (Human) Callsign: Warlock |
Destroyed Wolf-02 - Fighter Pilot Lt. Rath ch'Oshysrek ♂ (Andorian) Callsign: Turret |
Disabled Wolf-03 - Element Leader Lt. Bror Truggess ♂ (Tellarite) Callsign: Wedge |
Disabled Wolf-04 - Fighter Pilot Lt. Irina ♀ (Deltan) Callsign: Frost |
Destroyed Wolf-05 - Flight Leader Lt. R'rora ♀ (Caitian) Callsign: Whiskers |
Destroyed Wolf-06 - Fighter Pilot Lt. JG Xaikin Chaff ♂ (Bolian) Callsign: Sneaky |
Defected to the Theurgy Wolf-07 - Element Leader Lt. JG Donna Petterson ♀ (Human) Callsign: Chance |
Defected to the Theurgy Wolf-08 - Fighter Pilot Ens. Isel Nix ♀ (Vulpinian) Callsign: Foxfire |
Destroyed Wolf-09 Flight Leader Lt. JG Amator Barcor ♂ (Angosian) |
Destroyed Wolf-10 Fighter Pilot Ens. Tel Kaifur ♂ (Cygnian) |
Disabled Wolf-11 - Element Leader Lt JG. Marana ♀ (Risian) Callsign: Pulsar |
Disabled Wolf-12 - Fighter Pilot Ens. Ozel Sarea ♂ (Bajoran) Callsign: Banshee |
Defected to the Theurgy Wolf-13 Flight Leader CWO3 Liliana Walton ♀ (Human) |
Defected to the Theurgy Wolf-14 Fighter Pilot Lt. JG Sephiria Arn ♀ (Trill) |
Defected to the Theurgy Wolf-15 Element Leader Lt. JG Logan Hale ♂ (Human) |
Defected to the Theurgy Wolf-16 Fighter Pilot Lt. JG Jhozahosh sh'Avhennes ♀ (Andorian) |
The Grey Wolves Squadron & the Tribble Squadron
Before the USS Resolve' was thrown into unknown space by a spatial anomaly, the Grey Wolves Squadron consisted of eighteen fighter pilots and just as many RIOs. They flew Mk II Valkyries at first, but over the three-year voyage, the loss of many fighters forced them to form a secondary squadron, the surviving pilots flying Type-8 Shuttles with several modifications. The shuttle pilots that flew these shuttles were named Tribble Squadron, and they were led by Krystal Tancredi, callsign "Meony", who reported to the SCO, Daniel Havenborn, callsign "Salvo". As of the Battle of Starbase 84, the squadron ceased to be, instead being integrated into the Lone Wolves Squadron.
See below for the status of the Grey Wolves at the end of the Battle of Starbase 84:
| GREY WOLVES SQUADRON (DISBANDED) AC-307 Mk II Valkyries | |||
| Wolf-01 Squadron Commander Lt. Daniel Havenborn ♂ (Human) |
Destroyed Wolf-02 Fighter Pilot (KIA) Lt. JG Michael Sanders ♂ (Human) | ||
Destroyed Wolf-03 Flight Leader Ens. K'Ren ♀ (Caitian/Human) |
Destroyed Wolf-04 Fighter Pilot (KIA) Lt. JG Demetria Daniels ♀ (Human) |
Destroyed Wolf-05 Fighter Pilot (KIA) Ens. T'Iya ♀ (Vulcan) | |
| TRIBBLE SQUADRON (DISBANDED) Modded Type-8 Shuttles | |||
Destroyed Tribble-01 - Tribble Commander  Ens. Krystal Tancredi ♀ (Human) |
Destroyed Tribble-02 - Shuttle Pilot (KIA) Ens. Ara Laurent ♀ (Human) |
Destroyed Tribble-03 - Shuttle Pilot (KIA) CPO Kimberley Phillips ♀ (Human) | |
Destroyed Tribble-04 - Shuttle Pilot (KIA) PO1 Sophia Cortez ♀ (Human) |
Destroyed Tribble-05 - Shuttle Pilot (KIA) PO2 Dermot Lanier ♂ (Human) |
Destroyed Tribble-06 - Shuttle Pilot (KIA) CPO Kiera Thurmane ♀ (Human) | |
The White Wolves Squadron
When the USS Theurgy supposedly defected to the Romulans in November of 2380, orders came to Luna Shipyards that the twenty prototype Valravn fighters needed to be put into field duty, since the Theurgy's Mk III Valkyries were better than what the rest of Task Force Archeron had in terms of superiority fighters. So, the White Wolves Squadron ceased to be test pilots and were instead commissioned to the USS Orcus, which was supposed to join Task Force Archeron and hunt down the Theurgy.
In late February of 2381, the USS Orcus found the task force adrift, orbiting Theta Eridani IV without means of communication or propulsion. They had been affected by a computer virus, and it was only with the help of the USS Orcus "clean" software that the entire task force could exit orbit and take up the hunt again. Task Force Archeron immediately set a course towards Starbase 84 - meaning to intercept the Theurgy if Captain Ives had decided to put the advanced Theurgy-class starship of in his Romulan masters' hands.
At the Battle of Starbase 84, eight Valravn fighters defected to the USS Theurgy, being integrated into the Lone Wolves Squadron. See below for the status of the White Wolves at the end of the Battle of Starbase 84:
| WHITE WOLVES SQUADRON (DISBANDED) AC-477 Mk I Valravns | |||
| Wolf-01 Squadron Commander Lt. Talidenai zh'Idenna ♀ (Andorian) |
Wolf-02 Fighter Pilot Lt. JG T'Zantha ♀ (Vulcan) |
Wolf-03 Element Leader Lt. JG Amator Barcor ♂ (Angosian) |
Wolf-04 Fighter Pilot CWO3 Liliana Walton ♀ (Human) |
| Wolf-05 Flight Leader Lt. JG Devyrie Okhala ♀ (Human/Romulan) |
Wolf-06 Fighter Pilot Lt. JG Sephiria Arn ♀ (Trill) |
Destroyed Wolf-07 Element Leader (KIA) Lt. JG Leele Vovk ♀ (Human) |
Wolf-08 Fighter Pilot Ens. Tel Kaifur ♂ (Cygnian) |
| Wolf-09 Flight Leader Lt. JG Alessia Garcia ♀ (Human) |
Destroyed Wolf-10 Fighter Pilot (KIA) Lt. JG R'Meia ♀ (Caitian) |
Wolf-11 Element Leader Lt. Jg Logan Hale ♂ (Human) |
Wolf-12 Fighter Pilot Lt. JG Jhozahosh sh'Avhennes ♀ (Andorian) |
| Wolf-13 Flight Leader Lt. JG Cameron Ward ♂ (Human) |
Wolf-14 Fighter Pilot Ens. Esa Ojanpera ♂ (Bajoran) |
Wolf-15 Fighter Pilot Ens. Minjae Soh ♂ (Human) |
Wolf-16 Element Leader CPO Chatrine Palm ♀ (Human) |
Destroyed Wolf-17 Flight Leader (KIA) Ens. James Einhorn ♂ (Human) |
Destroyed Wolf-18 Fighter Pilot (KIA) Unknown White Wolf |
Destroyed Wolf-19 Element Leader (KIA) Unknown White Wolf |
Destroyed Wolf-20 Fighter Pilot (KIA) Unknown White Wolf |
The Dor'GhItlh Squadron
Before the Harbinger's crew were named outlaws and persecuted across the Alpha quadrant, the Dor'GhItlh Squadron was only one of four squadrons in Starfleet's 104th Fighter Attack Wing. What was unique to Wing Commander Kilinvoss' pilots were that they exclusively flew solo in thier Mk II Valkyries, i.e. having any RIOs in the back seat of their cockpits, and this remained true for the survivors in the Dor'GhItlh Squadron. The squadron as of February 2381, before the first battle with the USS Calamity is listed below. At that point, the 48 pilots strong Wing commissioned to the Harbinger had been reduced to twelve pilots, and after the battle, they were only eight, since Eli Cunningham, Harry Ezi, Toman Fal, and Teena Mod were KIA.
As of the final battle with the USS Calamity, all fighter pilots in the Dor'GhItlh Squadron were killed in action, except for Christopher Slayton, callsign "Husker", who defected to the USS Theurgy, becoming a pilot in the Lone Wolves Squadron and later the Lone Wolves Squadron.
Below is the Dor'GhItlh Squadron shown as of February 2381:
| DOR'GHITLH SQUADRON (DISBANDED) AC-307 Mk II Valkyries | |||
Destroyed Wing Commander/SCO (KIA) Lt Cmdr. Phanatos Kilinvoss ♂ (Human) Callsign: Phantom |
Fighter Pilot Ens. Christopher Slayton ♂ (Human) Callsign: Husker Defected to the Theurgy |
Destroyed Element Leader (KIA) Lt. JG Daniel Ritwer ♂ (Human) Callsign: Riptor |
Destroyed Fighter Pilot (KIA) Lt. JG Lukas B. Reed ♂ (Human) Callsign: Bleed |
Destroyed Flight Leader (KIA) Ens. Andrew Sullivan ♂ (Human) Callsign: Smoke |
Destroyed Fighter Pilot (KIA) MCPO Frida Armistead ♀ (Human) Callsign: Freya |
Destroyed Element Leader (KIA) Ens. Gregory Tilliander ♂ (Human) Callsign: Titan |
Destroyed Fighter Pilot (KIA) Ens. Rillian Hav ♀ (Human) Callsign: Riptide |
Destroyed Flight Leader (KIA) Lt. JG Eli Cunningham ♀ (Human) Callsign: Liquidus |
Destroyed Fighter Pilot (KIA) Ens. Harry Ezi ♂ (Human) Callsign: Hawk |
Destroyed Element Leader (KIA) Ens. Toman Fal ♂ (Trill) Callsign: Spectre |
Destroyed Fighter Pilot (KIA) CPO Teena Mod ♀ (Bolian) Callsign: Tempest |
