SHIPS OF THE STARFLEET

Small Craft Edition

2414
The Standard Reference Guide To The Small Craft of Starfleet
Ships of the Starfleet
Small Craft Edition

By The Red Admiral

Starfleet Operations/Advanced Starship Design Bureau

Copyright © 2414 Starfleet Department of Technical Services

Memory Alpha Catalogue Data:

UFPI ITP/SP SOTS2414-SCE

This edition of Ships of the Starfleet is authorized for viewing only in member star systems of the United Federation of Planets, its territories and possessions, affiliated star systems and select
independent or neutral star systems.
This publication follows the form and layout of the Ships of the Star Fleet publications published by Mastercom Data Center. Though inspired in part by these works, the publication is not intended as a copyright infringement
in any way shape or form.

This publication includes data and images from Paramount Pictures and various other sources. A complete list can be found in the Bibliography at the end. Any display of copyrighted materials is not intended as an
infringement on the rights of the respective copyright holders in any way shape or form.
SHIPS OF THE STARFLEET
Small Craft Edition
Table of Contents
State of the Fleet—8

Shuttlecraft
Type 6 Shuttle—10
Type 7 Shuttle—11
Type 8 Shuttle—12
Type 9 Shuttle—13
Type 12 Cargo Shuttle—14

Runabouts
Danube class Runabout—16
Pulsar class Runabout—18

Starfighters
Valkyrie class Attack Fighter—20
Peregrine class Attack Fighter—22
Omega class Heavy Bomber—25
Raptor class Space Superiority Fighter—27
Crusader class Medium Bomber—29
Avenger class Space Superiority Fighter—31
Archangel class Attack Fighter—33

Bibliography—35
STATE OF THE FLEET

Starfleet’s small craft inventory is today, more varied and diverse than ever before. deal of attention since the early 24th Century, astro-political events unfolding as they
The wide range of mission profiles undertaken by starships of the fleet underlie the need for have, driving continued development in this arena.
an equally wide range of small craft with varying operating ranges, capable of providing
the fullest possible level of support for those missions.

As with starship design and construction, the design and construction of Starfleet’s
small craft is influenced to a certain degree by the political realities of the day. The
Dominion War pressed home the need for more robust offensive/defensive packages,
longer operating ranges and higher maximum speeds. This pushed continued
development of not only specialized craft such as starfighters and cargo shuttles, but
comprehensive refit/upgrade programs as well.

Prior to 2368, small craft development was surprisingly stagnant. The shuttlepods and
larger shuttlecraft in service were fairly limited in their operational capabilities and suffered
from high attrition. The Danube class Runabouts which entered service midway through
that year were designed specifically to correct many of those deficiencies.

Slightly smaller than a cargo shuttle, the Danube class featured an interior that could
comfortably fit a crew of up to 4, shields & weapons that were unmatched in power by any
previous shuttlecraft design and an operating range that allowed it to conduct missions of
extended duration alone or otherwise. Its maneuverability in various planetary atmosphere
was a notable design breakthrough.

The success of the Danube drove the continued development of shuttlecraft, with
the Type 8 (a refit of the Type 6, entering service in 2370) and Type 9 (also entering service
in 2370) becoming the new fleet standards, eventually replacing the older Types 6 & 7 in
service.

As opposed to standard shuttles and runabouts, starfighters have garnered a great

SHUTTLECRAFT

5 types of shuttlecraft are currently operated by Starfleet—the Type 6, 7, 8 and 9

personnel shuttles and the Type 12 Cargo Shuttle. The former 2 ended their production runs
in 2368 and 2370 respectively. The future of the Type 8 is uncertain at this point. A
moderately refitted version of the Type 6, the Type 8 has been favored in the past by the
SFMC for special operations work, but for all intensive purposes, has been eclipsed in
operational capability by the Type 9.

The Type 9 is currently the most advanced shuttlecraft design in service. Influenced
heavily by the engineering behind the Danube class and designed with many of the latest
technological advanced in mind, the Type 9 is expected to replace the preceding three
types entirely once specific production goals are reached.

While the Type 9 remains the most advanced, the Type 12 currently holds the
distinction of being the largest shuttle in service, designed expressly for transport duties. The
design’s size, capabilities and overall versatility saw the parallel development of an ‘/M’
variant for Starfleet Medical.

RUNABOUTS

An outgrowth of small craft development spurred by the introduction of the Danube

class, this area has seen the most attention by designers and engineers in recent years
thanks to the combination of size, capability, versatility and operating range—making them
ideal for both general & specialized support duties as well as for use as cutters (cutters
being small patrol craft for intra-system use). Danube, in service since 2368, was joined by
the Pulsar class in 2396.

STARFIGHTERS

Integral to Starfleet’s continued defense and also key tactical tools where power
projection is concerned, Starfleet’s Starfighter Command currently operates 7 distinct
fighter classes which can roughly be separated into two categories—‘old’ and ‘new’.

The ‘old’ comprise the Valkyrie, Peregrine and Omega classes. While all have been
shown to be amazingly capable in service, Valkyrie and Peregrine’s lack of warp capability
as well as their relatively cumbersome natures in relation to repairs and refits/upgrades
have become operational hinderances.

On the other hand, the ‘new’, made up by the Archangel, Avenger and Crusader
classes embody the same highly capable, adaptable mindset that has become a crucial
guiding force in the design of Starfleet’s newest starships. With all 3 being fully warp
capable, there is currently discussion brewing within Starfighter Command over the possible
retirement of 2 of the former—with Archangel and Avenger/Raptor fulfilling the same
respective roles.
TYPE 6
SHUTTLECRAFT

Class Type 6
Classification Shuttlecraft

Service 2356-
Number Active 790

The first shuttlecraft to be built in the 24th century, the Type 6 could be considered Length 6m
more a radical reworking of the venerable Type 3 (which entered service in 2280 and Beam 4m
didn’t end production until 2310) rather than a separate class in its own right. Height 3m
Decks
Even to a casual observer, the external similarities are clear. The middle third of the Mass 3 metric tons
craft was removed, shortening the overall length, and newer engine nacelles were utilized.
To their credit though, these shuttles were the first to feature duranium/tritanium
construction and feature isolinear computer systems. Compliment 1 + 6 passengers

Despite the smaller number of passengers able to be carried, the Type 6 proved to Armament 2 Type IV Phaser Emitters
be extremely capable in service and popular with pilots—featuring a sleek, modern
cockpit design and an excellent forward field of view. Defense Standard Deflector Shield System
Systems total capacity 500 TerraJoules
Though production of the Type 6 ended in 2368, 790 examples currently remain in
service. All are expected to be retired by 2420. Light Duranium/Trititanium Single Hull
TYPE 7
SHUTTLECRAFT

Class Type 7
Classification Shuttlecraft

Service 2359-
Number Active 812

Introduced in 2359, the Type 7 shuttlecraft was developed as a slightly larger, heavier Length 9m
variant of the Type 6—which was rapidly becoming the new standard throughout the fleet. Beam 4m
Slightly improved computer & propulsion systems are featured as are heavier phaser Height 3m
emitters and a more powerful deflector shield generator. Decks
Mass 4 metric tons
Production of the Type 7 ceased in 2371 in favor of the Type 8. 812 examples remain
in service.
Compliment 1 + 6 passengers

Armament 2 Type V Phaser Emitters

Defense Standard Deflector Shield System

Systems total capacity 750 TerraJoules

Light Duranium/Trititanium Single Hull

TYPE 8
SHUTTLECRAFT

Class Type 8
Classification Shuttlecraft

Service 2371-
Number Active 6,763

Whereas the Type 6 was the first shuttlecraft design launched in the 24th Century, the Length 9m
Type 8 was the first purpose built design to be launched—abandoning the structure of the Beam 4m
Type 3 entirely. The dimensions however, remained precisely the same and from an Height 3m
external perspective the Type 6 and Type 8 still bear a rough resemblance to one another. Decks
Mass 4 metric tons
The Type 8 was introduced in 2371, a mere 6 months after the Intrepid (CL 74600)
class. It was no coincidence then that designers chose to take advantage of
Compliment 1 + 6 passengers
technological advances employed on that class—namely bio-neural computer systems.
Advances in engineering and construction techniques/processes also permitted the use of
a rigid, integrated hull structure. Paired with improved propulsion systems, the Type 8 is able Armament 2 Type V Phaser Emitters
to operate much more efficiently in planetary atmospheres compared to previous types.
Equipped with the same Type V Phasers and improved Deflector Shield Generator Defense Systems Standard Deflector Shield System
introduced on the Type 7, the Type 8 has since gone on to prove itself a worthy successor total capacity 750 TerraJoules
to the previous 2 types, becoming widely adopted, especially among outposts, space
stations and starbases throughout the Federation. Light Duranium/Trititanium Single Hull

The Type 8 was projected to be replaced by the Type 9 beginning in 2395, but
several considerations; namely its effectiveness as a short-range/intra-system Special Ops
craft and its larger passenger capacity (6, vs the Type 9’s 2) led to a production extension.
With wartime attrition remaining above average for shuttles and small craft overall, it’s
expected that production of the Type 8 will continue for some time to come.
TYPE
TYPE 9
9
TYPE 9
SHUTTLECRAFT
SHUTTLECRAFT
SHUTTLECRAFT
TYPE 9 Class Type 9
SHUTTLECRAFT Class
Classification
Class
Classification
Type 9
Shuttlecraft
Type 9
Shuttlecraft
Classification Shuttlecraft
Service 2370L
Service
Number 2370L
Active 7,867
Service 2370-
Number Active 7,867
Number Active 7,867
Length
Class 9.17m
Type 9
Length
Classification 9.17m
Shuttlecraft
Beam Length 3.8m
Beam 3.8m9m
HeightBeam 2.95m 4m
The mostThe advanced shuttlecraft currently in Starfleet service, development of the Type 9 Height
Service 2.95m
2370L
The most most advanced
advanced shuttlecraftcurrently
shuttlecraft currently in in Starfleet
Starfleet service,
service,development
developmentofofthe the Type 9 Decks Height 1
Decks Active 7,867
Number 1 3m
actuallyactually
predated the Type
predated the 8 Type
by 2 years
8 by 2 (beginning
years in 2368
(beginning in compared
2368 compared to 2370
to for the
2370 for Type
the Type
Type 9 actually predated the Type 8 by 2 years (beginning in 2368, compared to 2370 for Decks
8). This was
8). duewas
This in part
due to
in the more
part to the extreme
more requirements
extreme requirementsguiding the Type
guiding the 9 Development
Type 9 Development Mass Mass 1.85 metric tons
2metric
metric tons
the Typeand8). This was due in Length 9.17m
& part to the more stringent requirements guiding the Type 9’s Mass 1.85 tons
Project theand
Project research
the researchdevelopment
& developmentneeded to help
needed to fulfill
help those
fulfill requirements.
those requirements. Beam 3.8m
Development Project as well as the research & development needed to help fulfill these
requirements. The most advanced shuttlecraft currently in Starfleet service, development of the Type 9 Compliment Height
Compliment 22.95m +2 2+ passengers
2 passengers
True interstellar flight plus
True interstellar enhanced
flight plus enhanced survivability are attributes
survivability are attributesnormally
normally associated
associated withwith Decks
Compliment 1 1 + 2 passengers
small starships. actually
Applying predated
them to the Type craft
small 8 by 2 years (beginning in 2368 & compared to 2370 for the Type
small starships. Applying them to smallrequires takingtaking
craft requires power power engineering
& engineering conL conL Armament
Armament 3 Type
3 TypeVV Phaser
PhaserEmitters
Emitters
True interstellar
8). Thisflight
was due plus inenhanced
part to the moresurvivability
extremeare attributes
requirements normally
guiding attributed
the Type to
9 Development
straints into consideration.
straints into consideration. More often
More than
oftennot,thanthese constraints
not, these have
constraints been
have so restrictive Mass
so restrictive
been 1.85 metric tons
2 MicroLTorpedo
2 MicroLTorpedo Launchers
Launchers
small starships. Project
Applying themand the research
to small & development needed to help fulfill those requirements.
that development
that development projectsprojects
have been havecraft requires
canceled
been canceled taking
in their
power
in early
their &stages.
stages.
early engineering Armament 3 Type V Phaser Emitters
constraints into consideration. More often than not, these constraints have been so Compliment 2 + 2 passengers 2 Micro Torpedo Launchers
True interstellar flight plus enhanced survivability are attributes normally associated with Defense Defense SystemsStandard
Systems Standard DeflectorShield
Deflector ShieldSystem,
System, total
total capacity
capacity13,500
13,500TerraJoules
TerraJoules
restrictive
Significant that development
Significant
advances advances projects
in
in technology have
technology
during been
during
this canceled
this
period period
howeverin their
however early
resultedresultedstages.
in these
in&these constraints
constraints
small starships. Applying them to small craft requires taking power engineering conL Armament Light
Light Duranium/Trititanium
3 TypeDuranium/Trititanium
V Phaser Emitters Single Hull
Single HullShield System
being nullified.
being nullified. straints
Propulsion Propulsion
into advances advances
consideration. More along
along oftennew,
with with not,
than new, redesigned
these
redesigned constraints
reactors reactors
have
gave gave
beenthesothe Type
9 9
restrictive
Type Defense Systems Standard Deflector
2 MicroLTorpedo Launchers
Significant
theand
power advances
and speed in technology
designers during
were lookingthisfor
period inhowever,
production resulted
examples in these total capacity 13,500 TerraJoules
the power that
speed development
designers projects have
were looking been
for canceled
production their early
examples stages.ableable to achieve
to achieve a a
constraints
nominalnominalbeing
cruise speed nullified.
cruise ofspeed Propulsion
Warp of3,Warp
also 3,advances
also capable
capable along
of an of with new,
an emergency
emergency redesigned
speed speed reactors
of Warp
of Warp gave
4 for4 3for 3 Defense Systems Standard Deflector Shield System, total capacity 13,500 TerraJoules
the Type 9 the
hours. Significant
power and advances
speed in technology
designers were during this period however examples
seeking—production resulted in these
able constraints
to Light Duranium/Trititanium
Light Duranium/Trititanium Single Hull Single Hull
hours. being nullified. Propulsion advances along with new, redesigned reactors gave
achieve a nominal cruise speed of Warp 3 and an emergency burst speed of Warp 4 the
(3hrsType 9
3 Type V the powerEmitters
Phaser and speed designers
provided with were looking for offensive
an impressive production examples
punch, howeverable to achieve
the number a
max).
3 Type V Phaser Emitters provided with an impressive offensive punch, however the number
nominal cruise speed of Warp 3, also capable of an emergency speed of Warp 4 for 3
employed combined power requirements of these weapons precluded the installation of
employed combined hours. power requirements of these weapons precluded the installation of
the high
3 Type powerEmitters
V Phaser Deflector Shield System
provided featuredoffensive
an impressive on the Type 7 andCombined
punch. 8. To counter with thata defiL
the highciency,
power 2Deflector
foreward Shield
mountedSystem featured
microLtorpedo on the
launchersType 7
were and 8. To
installed. counter
The that
modern defiL
pair of forward
ciency, firing
3 Type
2 foreward micro-torpedo
V Phaser
mounted launchers,
Emitters a vastly
provided launchers
microLtorpedo with an more
were powerful
impressive offensive
installed. Deflector
punch, Shield
however
The modern thesuccesL
succesL number
System and impressive
employed overall agility
combined has led
power requirements Ltorpedos
toLtorpedos
the Type 9and
being
of these and their
used
weapons launchers
in the
precluded light were
theattack essentially
installation of
scaled down versions of their larger counterparts featuredtheironlaunchers
larger were and
starships essentially
first emL
the high power Deflector
role in the absence of comparable starfighters. Shield System featured on the Type 7 and 8. To counter that defiL
scaled down
ployed versions
on Danube
ciency, of their larger
2 foreward counterparts
mounted featured
microLtorpedo on larger
launchers starshipsThe
were installed. and first emL
modern succesL
ployed on Danube
agility has occasionally led to the Type 9 being used in the and
Ltorpedos lighttheir
attack role inwere
launchers certain comL
essentially
agilityAs is obvious with aled
has
batoccasionally
design
to the
scaled !down versions
scenarios.
this sleek,
Type interior
9 larger
of their being volume
used in thecompared
counterparts light attack
featured
torole
other
on larger in types
certain
starships
is
andcomL first emL
somewhat reduced, cutting the passenger capacity down to a maximum of 2 from the 4-6
bat scenarios.! ployed on Danube
of previous types.
agility
The sleek, has occasionally
contoured design ofledthe
to the
TypeType 9 being
9, while used in the
improving lightfield
warp attack role in certain
dynamics comL
has resulted
bat scenarios.
in contoured
The sleek, less overall design! volume,
interior cutting
of the Type the maximum
9, while number
improving warp of passengers
field dynamicsable
hasto be carL
resulted
ried down
in less overall to 2
interior compared
volume, to 6 the
cutting for previous
maximum types.
number of passengers able to be carL
The sleek, contoured design of the Type 9, while improving warp field dynamics has resulted
ried down to 2 compared
in less overall to 6 forvolume,
interior previous types.
cutting the maximum number of passengers able to be carL
ried down to 2 compared to 6 for previous types.
TYPE 12
CARGO SHUTTLE
(/M VARIANT)

In the latter half of the 24th Century, the development, deployment and great engineer and science officer or other mission specialist. In the middle of the cockpit, at the
success of the Danube class Runabout in service was a watershed moment in the history of aft end was a semi-circular freestanding auxiliary console used to control the two-man
Starfleet small craft development. Marginally larger than the Type 10 Cargo Shuttle, transporter platform also at the cockpit’s aft end as well as to control and monitor systems
featuring comprehensive multi-mission capabilities and able to travel at warp, Danube in the cargo hold.
seemed to spell the end to the development of specialized shuttlecraft altogether.
Similar to the aft section of a Danube class Runabout, the Type 12’s upper deck was
However, Starfleet’s logistical needs only multiplied followed the end of the designed as a crew cabin featuring a larger conference table in the center along with
protracted conflict between the Federation Alliance and the Typhon Pact in 2387. sleeping bunks (2 each) and food replicators (1 each) built into the port and starboard
Starfleet’s dual expansion/exploration initiatives in both the Gamma and Delta Quadrants bulkheads. Access between the decks in the forward section was facilitated by a two-
(the latter made possible thanks to the development of Quantum Slipstream propulsion), person lift and a ladder situated against the bulkhead positioned amidships, which
could only be sustained by a robust infrastructure—one component of which was separated the forward section from the cargo hold.
comprehensive transportation network that facilitated the timely movement of both
personnel and cargo between ships, colonies and fixed installations. Moving aft through the airlock chambers, the cargo hold itself was designed as one
large area, encircled by a catwalk and featuring ladders built into the bulkheads. To add
To that end, Starfleet’s Transport Command commissioned the ASDB to develop a versatility, the hold could be split into 3 separate section which could be hermetically
successor to the Type 10 with two clear goals—a vastly increased payload capacity of no sealed by specially calibrated forcefields—allowing for a variety of cargo types and
less than 50 metric tons and a nominal cruising speed of Warp 6 or better. With that in combinations to be carried. Total payload capacity for the Type 12 was a staggering 54
mind, development began at a breakneck pace in late 2388. metric tons or up to 550 cubic meters.

The resulting design which emerged a scant 10 months later in March of 2389 Entry and exit was facilitated by a standard personnel hatch along the port side and
became the largest shuttle launched to date, just barely eclipsing the Danube at 26 meters a large cargo hatch at the rear.
in length and 34 metric tons (empty) displacement. It also became the second small craft
to feature a 2-deck layout (the first being the Omega class Heavy Bomber). The shuttle’s size and versatility/adaptability prompted a request by Starfleet Medical
for a dedicated medical variant. Designated the Type 12/M, modifications included
The interior layout of the shuttle’s forward section was based loosely on the Danube removal of the sleeping bunks in favor of cryo-stasis chambers—permitting critically injured
class. The cockpit occupied the main deck and was arranged in a smooth-flowing ‘U’ patients to be stabilized until the shuttle reached a vessel or installation with more
shape, with positions for the pilot/flight controller (CONN) and operations manager (OPS) comprehensive treatment facilities—as well as conversion of the cargo section into a field
forward and 2 other positions along the port and starboard sides—usually occupied by an hospital featuring 6 full size bio-beds. This variant was deployed almost exclusively aboard
the Olympic (AH 55010) class Hospital Ship, but also selected other classes as well
depending on the specific mission requirements at hand.

Unique for a craft of this size and one designed expressly for transport purposes, both
the Type 12 and the /M variant are equipped with a high capacity deflector shield system,
6 Type VI Phaser Emitters and 2 Micro-Torpedo Launchers, ensuring survivability and
providing a starship so equipped, with additional defensive/offensive capability.

Class Type 12
Classification Cargo Shuttle

Service 2389-
Number Active 3,750 (‘/M’ variant – 2,875)

Length 26m
Beam 13m
Height 8m
Decks
Mass 28 metric tons

Compliment 1 + 50 passengers
1 + 40 passengers (‘/M’ variant)

Armament 6 Type VI Phaser Emitters

2 Micro Torpedo Launchers

Defense Systems High Capacity Deflector Shield System

total capacity 69,311 TerraJoules

Light Duranium/Trititanium Single Hull

DANUBE
CLASS RUNABOUT

The most important small craft development in over a century, the introduction of
the Danube class in 2368 successfully bridged the gap between small craft and starships— Given Danube’s range and capabilities, it was the first choice for commanders of
providing a warp-capable craft that had all the multi-mission functionality of a starship, but starships and installations located in various frontier regions, including Deep Space Nine. In
in a package that was only somewhat larger than the shuttlecraft of the day. 2369 after Starfleet assumed command of the station at the behest of the Bajoran
Provisional Government, the Starship Enterprise (CH 1701-D) offloaded three of these
A design study begun by the ASDB in 2363 aimed to produce a small craft capable runabouts—the Rio Grande (CU 72452), Ganges (CU 72454) and Yangtzee Kiang (CU
of fulfilling a wide range of missions, most notably scientific transport, research and study as 72453). Piloted by Commander Benjamin Sisko and Lieutenant Jadzia Dax, the Rio Grande
well as intelligence gathering, tactical reconnaissance and special operations support. was the vessel responsible for the discovery of the Bajoran wormhole and the first
Such a craft would need to be warp-capable, with a standard operating range at least Federation vessel to travel to the Gamma Quadrant.
double that of existing personnel shuttles and be capable of sustained independent
operations. To support disaster relief, emergency response, special ops insertion/extraction A year later, the Rio Grande—again, piloted by Commander Sisko—was conducting
and other associated mission scenarios, it was also deemed essential to make the craft a planetary survey in the Gamma Quadrant when it became the first Federation vessel to
large enough to support a reasonable number of passengers. encounter the Dominion. After Sisko and his party were captured by the Jem’Hadar, the
Mekong (CU 72617) and Orinoco (CU 72905) escorted the Starship Odyssey (CH 71832) on
The ASDB’s design, which was finalized in late 2364, was the first small craft design to an emergency rescue mission. Despite the two runabouts having been equipped with
make modularity a priority. Aft of the cockpit, Danube consisted of the propulsion extra stores of Photon Torpedoes, they and the Galaxy class Odyssey were quickly
assembly and could equip any number of large, swappable multi-mission modules that ran overwhelmed by a trio of Jem’Hadar Attack Ships—the Mekong sustaining severe damage
the gamut from additional sleeping bunks and medical accommodations to cargo storage and the Odyssey destroyed. Though the Danube class’ attrition rate remained rather high
and specialized scientific equipment. Going further, Danube—like the larger Nebula (CA for the next decade, the Rio Grande was the only one of Deep Space Nine’s original 3
60140) class—could be equipped with a number of specialized external modules mounted runabouts to survive the tumultuous decade.
dorsally that, depending on configuration, could augment the craft’s communication,
sensor or tactical capabilities. By 2380, Danube’s production had become so prolific, that it began to find
increasing use in various intra-system roles, including patrol and interdiction. This led
Launched in 2365, the prototype (CU 72000) underwent extensive flight-testing and Starfleet Command to change its classification type from ‘runabout’ (which differed little
conducted strenuous shakedown trials at the Saturn Flight Range. Upon their successful from ‘shuttlecraft’) to ‘cutter’.
completion, full class production commenced and the class was well dispersed throughout
the fleet by 2368. In the Borg Invasion of 2381, starships that formed the spearhead of Starfleet’s
response to the initial invasion had wisely offloaded their Danube class craft in exchange
for more potent starfighters. The runabouts then, participated in predominantly defensive
operations—acting as early warning platforms for planetside colonies and settlements, as
well as helping to evacuate smaller stations and other spaceborne installations. In the
Invasion’s aftermath, with the Borg’s devastation extensive and Starfleet’s existing resources
stretched thin, Danube’s sheer numbers were a great asset—runabouts taking on patrol,
command and control, transport and humanitarian relief duties, among many others, on a
system-by-system basis.

In 2396, the Danube’s perceived successor—the Pulsar class entered service and
brought with it significant technological advances. A mere 6 years earlier when the Valiant
(DD 98940) class was launched, the notion of Quantum Slipstream propulsion equipping
anything smaller that a Destroyer was considered ludicrous in the extreme. In 2395 though,
the launch of the Pegasus and Proxima corvette classes—half the size of Valiant—proved
that it could be done and it didn’t take long then for the momentum to engulf certain small
craft types.

In a shrewd, but predictable move to boost force strength, Danube class production
was halted for a period while the ASDB completely overhauled the base design—
incorporating necessary changes to not only support the new propulsion system, but
advanced sensor and communications equipment as well as more powerful shield
generators and weapon emplacements that equipped Pulsar.

Currently it is estimated that of the 2,450 Danube class runabouts active, a full third— Class Danube
roughly 817—have not been upgraded to this new standard. Starfleet Command has set Classification Cutter/Runabout
2417 as the definitive deadline by which time all existing examples are to be upgraded.
Service 2368-
Number Active 2,450

Length 23m
Beam 14m
Height 6m
Decks
Mass 159 metric tons

Compliment 1 + 40 passengers

Armament 6 Type IV Phaser Emitters

2 Micro Torpedo Launchers

Defense Systems Standard Deflector Shield System

total capacity 56,700 TerraJoules

Light Duranium/Trititanium Single Hull

PULSAR
CLASS RUNABOUT

Succeeding the venerable Danube (CU 72000) class in the majority of front-line helm/operations and mission operations to port and starboard respectively, with a station
applications, the Pulsar class has reaffirmed the relevance and utility of small craft as part for a flight engineer aftwards. All stations are highly configurable—one proposed layout
of Starfleet’s overall deployment doctrine—providing enhanced support and maximum having the forward station configured for the tactical/weapons officer, with the
flexibility across the entire multi-mission spectrum. pilot/navigator occupying the portside aft station.

Conceived in 2394, Pulsar was the product of a development project that aimed to Moving aft from the cockpit, was a small antechamber with personnel hatches to
address Danube’s speed limitations and tactical deficiencies and more generally, to port and starboard and an ingress/egress ramp in the center of the floor. Continuing on
provide a flexible medium-long range support platform that would be better able to match was another compartment of equal size that contained a 2 person transporter platform in
the capabilities of the new generation of starships then entering service. the center, equipment storage along the starboard bulkhead and a head to port. A large
crew compartment was featured next—with three double-bunk staterooms and a small
The period immediately following the end of open hostilities with the Typhon Pact survey lab followed up by the standard aft compartment of Danube—featuring 2 more
saw Starfleet focusing on two main areas of concern: rebuilding and redevelopment of double-bunks recessed into the bulkhead along with a conference table and requisite
infrastructure and overall fleet strength (numerically and tactically). Whereas Danube was food replicators. All told, Pulsar was capable of embarking up to 60 passengers in an
the product of a more idealistic, exploration-focused design ethic that placed an extra emergency compared to the 40 of Danube.
emphasis on technology, Pulsar was decidedly no-nonsense--focusing strictly on combining
technology, tactical strength and multi-mission functionality in a single, efficient end The most notable feature of Pulsar was its completely redesigned drive system. A
product. common and accepted drawback of small craft new and old was their lack of FTL (faster-
than-light) propulsion, or in included, FTL propulsion that was severely constrained in terms
Aesthetically, Pulsar was streamlined a great deal compared to Danube. From a of acceleration as well as nominal cruising and overall top speeds. This could be attributed
dorsal/ventral perspective, the design bore a great deal of similarity to 20th century Earth’s to both technology and engineering issues, however since the introduction of Danube in
Space Transportation System operated by NASA. The main body, 41 meters in length, had 2368, considerable strides had been made in both fields—thanks to Quantum Slipstream
a smooth ‘coke-bottle’ shape, tapered sharply at the fore end, with the engine nacelles Propulsion.
mounted dorsally at the rear—taking a cue from the Raptor class starfighter.
Intended to propel starships at speeds and across distances previously unimaginable,
The cockpit design was borrowed directly from the Flyer class shuttlecraft and the revolutionary new propulsion system required not only engines of a vastly sophisticated
featured a two-tiered layout with space for up to four crew members, though as with design and that were meticulously engineered, but a computer system more powerful and
Danube, Pulsar was designed to be operated by as few as one crew member. The complex than anything previously employed. Advancements in engine design and
pilot/navigator was situated on the lower tier, front and center, surrounded on three sides computer operation began trickling down to the small craft arena after those two
by control consoles, while up a narrow ramp to the rear were the remaining three stations—
attributes had been refined for the smallest ships yet—the Pegasus and Proxima class
corvettes.

A correspondingly powerful reactor not only provided power to the engines and
other essential systems, by to 6 Type VII Phaser Emitters and 2 forward-firing Micro Torpedo
Launchers. The most powerful weapons of this type that have been installed aboard a
small craft, they put Pulsar on the same level as many of the older starship classes
deployed during the Dominion War, including the Miranda class—the greater total power
output from the advanced reactor core increasing the amount of raw energy able to be
directed through the emitters. Naturally, along with the more powerful weapons was an
improved Deflector Shield System, capable of absorbing an additional 11,200 TerraJoules
over that equipping Danube (67,900 vs 56,700).

The sensor suite also received a great deal of attention. Like with the phaser emitters,
Pulsar’s sensor arrays compared favorably with those employed aboard some starships—
with maximum range and resolution setting far eclipsing those aboard any current or
previous craft in the same size class. Passive scanning, detection and tracking capabilities
were a fairly new development. Devised for and intended to upgrade existing (and new
build) Defiant (DD 74205) and equip new Valiant (DD 74300) class Destroyers, these
functions strengthened Pulsar’s hand a great deal. In spaceborne operations, the craft
gained a sharper defensive edge—reportedly being tested with top-secret interphasic
cloaking technology, though this has never been confirmed. On the ground and in many
planetary atmospheres, Pulsar became an enhanced support tool for ground troop
formations, scientific expeditions, humanitarian missions and many other rapid-response
scenarios.

Entering service in 2396, Pulsar replaced Danube in most front-line, deep-space

applications. Rather than retire the older class, the ASDB stripped Danube down, removed
the old propulsion, computer and sensor systems and replaced them with their newer
counterparts from Pulsar. Given Danube’s high-numbers in service—this effectively
quadrupled Starfleet’s capabilities in this arena and also freed up larger starships for other
uses.

Class Pulsar Mass 189 metric tons Armament 6 Type VII Phaser Emitters
Classification Cutter/Runabout 2 Micro Torpedo Launchers

Service 2396- Compliment 1 + 60 passengers Defense Systems Standard Deflector Shield System
Number Active 540 total capacity 67,900 TerraJoules

Length 41m Light Duranium/Trititanium Single Hull

Beam 18m
Height 5m
VALKYRIE
CLASS ATTACK FIGHTER

Developed in 2338 to fulfill a requirement for an agile and easy to produce craft to exhaustive process of specially calibrating and optimizing the engines for this new fighter,
fulfill interceptor duties, the Valkyrie class would go on to become one of the unsung codenamed Valkyrie. The engines themselves, among the most powerful sub-light units in
heroes of the ‘Lost Era’ as well as become the longest serving type of small craft in Starfleet use at that time, combined with Valkyrie’s sleek, low profile design resulted in one of the
service – production slated to end by the end of the year, in favor of the new Archangel fastest, most agile small craft in Starfleet service.
class.
Valkyrie was also an exercise in simplicity, tactically speaking. A pair of Type V
At this point in time, the famed Class V starfighter family (Wasp – Hornet – emitters was carried, mounted ventrally, one on either side of the engines along with a pair
Yellowjacket) had been in service for over 60 years. Tested in combat against aggressors of micro-torpedo launchers that were dorsally mounted, one each atop the ramscoop
from the major powers of the day (Klingons, Romulans, Kzinti) and improved continuously housings. The strict standards governing speed and agility however, precluded the option
since entering service, the fighter family had evolved into an extremely potent, effective of carrying full-size ordinance, such as the ubiquitous Photon Torpedo.
weapons system.
Equipped with an enhanced deflector shield system along with a standard ECM
By the turn of the century however, the technology underpinning these craft was well suite, the class entered service in late 2338 to much fanfare, gradually replacing the Wasp
out of date. The introduction of the Renaissance and Ambassador classes brought with class in Starfighter Command’s various Interceptor Squadrons (being the only such fighter
them incredibly advances in nearly every area of spacecraft design and engineering. type still produced and classed as an Interceptor).
Despite the Class V’s battlefield prowess, all three fighter were ‘over-engineered’ to such a
degree that extensive refitting was not only unfeasible, in some cases it was actually Embarked aboard the Curry and Midway class Carriers, Exeter class Battlecruiser and
impossible and thus, Starfighter Command directed the ASDB to design and construct an later the Korolev class Heavy Cruiser, Valkyrie squadrons were heavily utilized during the
entirely new fighter. While tactical prowess and maneuverability were very important Federation’s protracted conflict with the Cardassian Union—the Cardassian Guard’s Hideki
aspects of the new fighter’s design, Starfighter Command was absolutely adamant that class Corvettes no match for the smaller, faster Starfleet fighters.
the craft be simple to maintain and easy to build in large numbers, especially in critical
situations when time was of the essence. To that end, the primary computer system was While a great number of Valkyries were embarked aboard starships, the majority of
taken from the Type 3 shuttlecraft and with light modifications to handle the targeting and Starfighter Command’s assets were organized into wings and squadrons stationed aboard
countermeasure systems, was installed with no trouble. The engines, an important space stations, starbases and outposts throughout Federation space. Interceptor wings
component of any fighter, were designed and engineered by the Leeding Engines Ltd. and squadrons comprised of these fighters often formed the first line of defense for many
Subsidiary of Cochrane Warp Dynamics. Keeping the speed requirement strictly sub-light stations and outposts in far off frontier regions that saw little, if any, starship traffic.
not only lended to the simplicity of the fighter’s engineering, but also allowed engineers
more flexibility in the design and integration processes. Once finalized design blueprints The introduction of the heavier Peregrine fighter class in 2357 saw the Valkyrie
were delivered from Starfleet’s ASDB, Leeding engineers and technicians began an removed from many front line postings and redeployed in a more defensive posture
around key planets and throughout systems closer to the Federation’s core, including
Sector 001.

In 2367, following the annihilation of Starfleet forces at Wolf 359, Starfighter

Command’s 1st Interceptor Wing assigned to the Mars Defense Perimeter, engaged the
marauding Borg Cube in a futile attempt to prevent the leviathan from reaching Earth,
however all 72 fighters were destroyed in short order.

The 1st IW was soon reconstituted and fared much better in 2375 during the Dominion
War when forces of the Breen Confederacy launched an assault on Starfleet
Headquarters—Valkyrie’s speed and agility helping to drive off the Breen aggressors.

Throughout the war, Valkyrie played a supporting role to the slightly larger, heavier
armed Peregrine, but was a heavy participant in many battles nonetheless. A squadron,
comprising craft from the battlecruiser Atlantis (CB 2227) and other Starfleet vessels,
participated in the destruction of the Cardassian space station Sentok Nor in orbit of
Betazed during the battle to retake that planet in 2375.

Valkyrie finally found itself on equal footing with Peregrine in 2385 when the
Federation Alliance went to war against the Typhon Pact. As Starfleet was the only
interstellar naval force at the time that fielded starfighters, the navies of the Typhon Pact—
particularly those of the Gorn & Kinshaya—were extremely hard pressed to defend against
these small attackers, which inflicted considerable damage on enemy forces. During
many engagements, many a friendly wager was made between pilots of both fighter types
over who could inflict the most damage.

The success of Valkyrie during this conflict (which ended in 2387) not only spurred a
major Starfleet ally (the Klingon Defense Force) to begin fighter development of its own, but
heavily influenced the design and development of the Raptor class space superiority
fighter—the most advanced fighter class fielded by Starfleet.

Still serving faithfully and reliably to the present day, these fighters can be found in a
multitude of roles, from convoy escort, to patrol, reconnaissance and fleet escort in
unexplored regions—such as the Delta and Gamma Quadrants. Valkyrie class production
is slated to end by the end of the year in favor of the recently developed Archangel class.

Class Valkyrie
Classification Attack Fighter/Interceptor
Armament 2 Type V Phaser Emitters
Service 2338- 2 Micro Torpedo Launchers
Mass 3 metric tons
Defense Systems Standard Deflector Shield System
Length 17m total capacity 47,250 TerraJoules
Beam 11m Compliment 1
Height 3m Light Duranium/Trititanium Single Hull plus 5cm High Density Armor
PEREGRINE
CLASS ATTACK FIGHTER

Developed to fulfill the requirement for a medium fighter to supplement the Valkyrie a catamaran assembly to provide stability. Matching Valkyrie’s famed agility, Peregrine
class then in service, the Peregrine class Attack Fighter would go on to become the most improved upon this facet by including the capability of holding a sustained cruise speed of
widely deployed/utilized fighter class throughout the 24th Century. Warp 5 for up to 8 hours.

During the Federation-Cardassian War, the widespread deployment of the Valkyrie The armament of Peregrine was a delicate subject. The design requirements called
class Attack Fighter/Interceptor was credited with helping Starfleet gain the upper hand for heavier firepower than Valkyrie, yet engineers didn’t want to risk over-arming the craft—
relatively quickly. Highly agile and featuring a simple armament, these craft were the bane sending it too far into bomber territory and negatively affecting maneuverability. In the
of the Cardassian Guard. However, the Valkyrie was also the only fighter class that had end, designers and engineers settled on a (relatively) powerful forward facing Type V
been developed and deployed thus far in the 24th Century. Starfighter Command still Phaser Emitter, mounted ventrally, flanked by a pair of Pulse Phaser Cannons mounted
relied heavily on the Hornet and Yellowjacket classes to fill the precision assault and ventrally as well. Providing a heavy strike capability were two micro torpedo launchers
bombing roles respectively. Though extremely reliable, the ASDB faced increasing difficulty mounted dorsally at the aft end of the craft. Being self contained units with small 8-round
in maintaining and updating these craft—which dated to the mid 2270’s. This, combined magazines apiece allowed them to be installed atop the impulse engine housings.
with in-field performance data taken during multiple engagements against the Tholian
Navy, spurred Starfighter Command to accelerate the modernization of its forces and Designed from its inception as a two man craft, Peregrine featured an extremely
introduce a new heavier counterpart to the Valkyrie class. streamlined cockpit arrangement—so advanced at its inception, the design itself was
classified for almost two decades. The pilot occupied the portside (left) position while a
As Starfleet’s well known (and oft derided) ‘multi-mission’ design philosophy guided dedicated weapons officer was positioned to starboard. Both positions featured expansive
the design and engineering of its ships, Starfighter Command dictated that a similar ‘multi- wraparound control consoles with a central, re-configurable systems display between
role’ philosophy guide the design of its new fighter. Designers were therefore tasked with them. Improved systems software was soon developed which automated a number of
designing a craft capable of excelling in the attack, ground support and space superiority functions and provided the option of operating the craft with just a single crew member.
roles—while keeping resource requirements and ease of construction in mind. This basic cockpit design, with subtle alterations, would go on to be adapted for use in the
Type 9 shuttlecraft in 2370.
Design work began in mid 2366 and took just a scant 6 months to complete. The
finalized design took an aggressive, triangular form with two down-swept wings on either The fighter class entered service in 2367 aboard the Midway class initially, but soon
side, giving the new fighter—codenamed Peregrine—a profile vaguely similar to that of the operated from those ships only in a training capacity—the Curry class becoming the
Klingon D-11/B’Rel class Bird of Prey. Unlike Valkyrie—an extremely streamlined craft that primary operational platform.
integrated the engines within the hull—Peregrine featured an unorthodox arrangement,
with the warp engines embedded in the main body flanking the cockpit, while the impulse In the wake of the Borg Invasion of 2367, Peregrine became a part of Starfleet’s
engines were installed in large housings which extended aftwards and were connected by overall strategy to strengthen its defenses. Starfighter Command therefore devoted the
bulk of all its resources and shifted emphasis from other efforts, to the production and While the 4th Attack Wing may have been the most famed of the numerous
deployment of these fighters as well as accelerated pilot training to keep pace with Peregrine units in service, the bulk of operational Peregrines were concentrated in 4 other
production. Attack Wings divided between the 2nd and 3rd Divisions. In December of 2374, the 2nd—
under the command of Brigadier General Lance Deveraux—and 3rd—commanded by
Initial deployments were focused on the Federation-Cardassian border, which Brigadier General Thelin th’Zarath—found their over 500-fighter strong force stationed in the
remained a hotbed of low-level hostilities since at least 2360—in a situation roughly Chin’toka Star System. The assets that Starfleet had utilized in wresting control of that
analogous to that along the Federation-Klingon Neutral Zone during the 2280’s and into the system from the Dominion were now needed elsewhere, with a strong occupying force
2290’s. Operating primarily at the squadron level, these fighters and the carriers that they needed to protect the efforts of the Starfleet Corps of Engineers—at the time, working to
operated from, provided additional patrol and interdiction support that in turn, deterred fortify Chin’toka II. 10 months later, just days after the Breen mounted their daring raid on
any aggressive activity on either side. Earth, the Dominion mounted an operation to retake Chin’toka. The results were disastrous.
General th’Zarath was killed and both divisions were all but obliterated (along with the
Peregrine’s reputation was tainted though by astro-political developments just a few allied armada hastily sent to reinforce the system).
years later in 2370. The establishment of the Federation-Cardassian Demilitarized Zone and
the subsequent redrawing of the border between the two powers inadvertently resulted in Starfighter Command wasted no time in replacing these fighters. In December of
the possession of planets—and colonies on them—being transferred between both. 2375, the reconstituted 2nd Divisions—supported by 2 Destroyer Squadrons from the 12th
Civilian response to this was one of outrage, collectively giving rise to armed resistance and Fleet—along with a battalion of Starfleet Marines—captured Hontok Nor, the space station
resulting in the formation of the paramilitary group known as the Maquis. During the from which Dominion activity in the Badlands was coordinated.
group’s early days, various Starfleet personnel defected with a number of these fighters.
They were known to run heavily modified, with improved engines and exotic weaponry. One month later, in January of 2376, these fighters along with nearly all other
Starfighter Command assets were recalled in preparation for the Federation Alliance’s final
These events were overshadowed by even bigger developments in mid 2373. With assault on the Cardassian home system. If ever there was a battle during the war that
Cardassia announcing its alliance with the Dominion in July and the combined force of validated the worth of this class, this was it. Pilots, both experienced and novice, brought
both powers all but exterminating the Maquis beginning the next month, the Federation every bit of Peregrine’s destructive potential to bear on the Jem’Hadar, Breen and (initially)
Council moved quickly to repatriate all surviving Maquis members with no adverse Cardassians—many resorting to the same suicidal kamikaze tactics favored by the
consequences and pass the Emergency Powers Amendment. Jem’Hadar.

Among the many ramifications of the amendment—which moved Starfleet and the The war’s conclusion saw Starfighter Command enter a period of reconstruction and
rest of the Federation’s infrastructure towards a war footing—was increased production of rejuvenation along with Starfleet and the Federation as a whole. The Peregrine force,
more combat-oriented starships and small craft. For Starfighter Command, this meant battered and bruised as it was, still formed the core of the Command’s forces. Production
revamping its pilot training curriculum as well as drastically increasing production of both predictably slowed, as yard space and resources were given over to infrastructure needs.
Peregrine and the older Valkyrie class Interceptor. Schedules were ramped up and Assuming a more defensive posture, the Command deployed its fighters—including the
additional assembly locations were added—allowing Starfighter Command to field an Peregrines—to protect its own still fragile infrastructure: supply depots, outposts, major
estimated 460 additional Peregrines. shipping lanes, industrial bases and convoys.

Despite the fact that Peregrine was better armed than its older counterpart, The Borg Invasion of 2381 exacted a punishing toll on these starfighters, on an
Valkyrie’s sheer numbers helped it become the primary front-line fighter class deployed. In inconceivable scale. Despite the fact they were smaller and vastly more maneuverable
order for Peregrine to see action, Star Marshal Mezkan Traki had to overrule Vice Admiral than the gargantuan cubes and spheres used by the collective, their armament and
William Ross and forcibly detach an entire division to the 5th Fleet. Once this was done, defenses couldn’t come close to opposing the Borg—even in large wings and divisions.
Peregrine subsequently saw heavy action, with Operation: Return being their first large Not surprisingly then, most of the active Peregrines were lost—the majority in defense of
scale deployment. Federation colony worlds and installations. In light of these even more devastating losses,
Starfighter Command had no choice but to expand production once again—despite the
Throughout the war, the most famous unit to utilize Peregrines was the 4th Attack objections from some on the Federation Council.
Wing—the ‘Ferocious Fourth’. Under the command of Denobulan Colonel Groznik and
operating from the carrier Gettysburg (CVL 42261), this wing contained a record 12 aces. 4 years later, these losses had been rectified for the most part—when the Federation
Attached to the 5th Fleet, it held off a strong Dominion Force at Vulcan (First Battle of Alliance went to war against the Typhon Pact. This time, Peregrine was supplemented not
Vulcanis) led by the Cardassian 19th and 24th orders for a record 8 weeks before being only by Valkyrie, but the larger Omega class Heavy Bomber as well. Thanks to key victories
reinforced. won early on by Starfleet, Starfighter Command had the luxury of picking and choosing
where to deploy its forces. When it did choose to deploy forces in support of a battle, it did
so in overwhelming numbers—assuring victory irrespective of the starship classes Starfleet
deployed. Despite the Pact’s technological strengths—mostly in the form of
plasma torpedos, high power disruptors and cloaking technology—the lack
of equivalent small craft among any of the powers (the Romulan Imperial
Navy’s Shrike class notwithstanding), basically ceded tactical superiority to
the allies.

From the aftermath of this conflict and continuing to the present day,
Peregrine has been part of a balanced strategy focused on deterrence and
offensive power projection. The advent of fully warp-capable fighter classes
such as Raptor (2397) and Avenger (2400) though, has since seriously
diminished the value of Peregrine as a front-line fighter.

In keeping with the trend of streamlining its forces while continuing to

ensure tactical superiority, Starfighter Command is expected to begin
gradual retirement of Peregrine class fighters in favor of the new Archangel
class by the end of the year.

Class Peregrine Mass 27 metric tons Armament 2 Pulse Phaser Cannons

Classification Attack Fighter 1 Type V Phaser Emitter
2 Micro Torpedo Launchers
Service 2367- Compliment 1-2
Defense Systems Standard Deflector Shield System
Length 14m total capacity 67,600 TerraJoules
Beam 14m
Height 5m Light Duranium/Trititanium Single Hull
OMEGA
CLASS HEAVY BOMBER

The latest iteration of a design which initially entered Starfleet service in 2339, the to that of the Danube class Runabout, the pilot/navigator and weapons officer occupied
Omega class Heavy Bomber is the largest, most powerful and most versatile craft in the two forward stations while a further two positioned to port and starboard were
Starfighter Command’s inventory. configured for a flight engineer and ordinance specialist respectively. Positioned outside
the cockpit, on the opposite side of the bulkhead was the main 7-man transporter
In 2339, Starfighter Command issued a design brief for a new generation of trainer platform. The reactor systems, comprising the horizontal warp core, main energizers and
craft. When it became clearly unjustifiable to design and build a completely new craft antimatter storage were also situated on the upper deck.
from the keel up (given the low priority nature of the project), an existing civilian design was
modified to become the Alpha type Trainer. The lower deck was accessible by companionways to port and starboard and
featured a surprising amount of habitable space.
However, the craft that we know today has origins going all the way back to the
Federation-Cardassian War. The initial Alpha type Trainer was scaled up in size and At the fore end, four double-bunk crew cabins was arranged around a central
equipped with more powerful phasers, an increased micro torpedo loadout as well as wardroom with a small space dedicated to the computer core and accompanying
improved propulsion and computer systems. This put the enlarged version—known as the workstation to starboard along with a small 3-person transporter bay to port. Moving aft
Gamma type ‘Raider’—on par with the Cardassian Hideki class Corvette. was the armory, storage lockers, a small fabrication shop, medical bay, lower engineering
bay (housing deflector shield generators and other critical machinery) and a pair of heads
This version ceased production in the early 2360’s and the bulk of Starfleet’s inventory (port/starboard). Barrack-style accommodations were present midway back, featuring
was demilitarized and found its way into civilian hands as Starfighter Command pursued a double bunks and intended to house up to 36 extra personnel or ground troops depending
new strategy centered around smaller, more agile craft—typified by the Peregrine class on mission requirements. Also present was a small cargo bay and accompanying cargo
Attack Fighter. transporter.

However, the Gamma type’s infamous use by the Maquis prior to the Dominion War At the aft end was the ‘T’-shaped torpedo bay. It featured abundant storage for
combined with the heavy losses inflicted on the Peregrine force during that conflict both micro and full sized ordinance in racks along its horizontal axis along with a large
convinced Starfighter Command of the craft’s still relevant utility. In 2377, a comprehensive loading/ingress-egress ramp aftwards, situated between the impulse engines.
upgrade program was designed that would completely overhaul the craft. Now
designated Omega, it was reclassified as a heavy bomber charge with the precision Whereas Alpha featured a pair of wingtip-mounted Type V Phaser Emitters as its only
delivery of heavy ordinance on both fixed and mobile targets. armament, Omega expanded upon that by upgrading those to Type VI models and
adding a dorsally mounted Type VI Phaser Bank in the nose. Befitting its role as a bomber,
Still the same was the overall external and internal design. Featuring a spacious split the heavy weaponry was extensive for a craft of this size and comprised 4 torpedo
deck layout, the cockpit occupied the upper deck. Arranged in a rough ‘U’-shape similar launchers—2 forward, 1 each mounted on either side of the main body, with 2 more aft,
centrally mounted in between the impulse engines. Complimenting these were a pair of
Pulse Phaser Cannons, mounted forward, flanking the forward torpedo launchers. Omega
came capable of carrying a full range of heavy ordinance. Micro Torpedoes were
standard—fitted with both photon and quantum warheads—as well as full size Photon,
Quantum, Tri-Cobalt and Transphasic torpedoes depending on mission requirements.

Many of the existing craft that survived the Dominion onslaught were repatriated by
Starfleet and converted in earnest while a new production order was placed with several
shipyards within the Federation core systems. By 2381, Starfighter Command had equipped
4 full wings, the 1st, 3rd, 5th and 7th. During the Borg’s final invasion that year, Starfighter
Command deployed nearly all of its coreward assets—including these 288 bombers—in
defense of Earth. Subsequent to the UFP President’s order for all Federation & allied forces Class Omega
in Sector 001 to disperse (following the Borg’s adaptation to Transphasic Torpedoes), the Classification Heavy Bomber
Bomber force covered the withdraw of forces from the system.
Service 2377-
Along with the Valkyrie and Peregrine classes, Omega class Bombers participated
heavily in the 2385-87 war between the Federation Alliance and the Typhon Pact. Length 60m
Embarked primarily aboard the Essex and Excalibur Battleship classes, they participated in Beam 66m
a number of fleet engagements, but were primarily used planetside. In conjunction with Height 15m
various mixed wings of the 2 aforementioned classes, Omegas were used in support of
Starfleet Marines, against enemy ground installations, fortifications, vehicles and troop
formations. Mass 2,600 metric tons

In 2396, the 9th Bomber Wing was activated and permanently attached to newly
completed Starbase 601—the HQ of Starfleet’s Project ‘Full Circle’ and the hub of all Compliment 2
Federation and Starfleet activity in the Delta Quadrant. A similar move was made in 2398 27 metric tons
when Starfleet Command activated the 11th Bomber Wing attached to the planetside Armament 2 Type VI Phaser Emitters
Starbase 624 in Gamma Quadrant sector 27-M (in support of Mission: Gamma). This 1 Type VI Phaser Bank
increased the total number of Bombers fielded to 360 across 5 wings, not counting the 1
2 Pulse Phaser Cannons
untold number of additional craft embarked aboard various starships. 4 Torpedo Launchers

Despite the age of the basic design/layout underpinning Omega—and the fact that Defense Systems Standard Deflector Shield System
the equally aged Valkyrie and Peregrine are both slated to be replaced by a newer, more total capacity 109,800 TerraJoules
advanced fighter—its capabilities have been more than proven in the current incarnation’s
nearly 4 decades of active service and ensure a continued production run for the Light Duranium/Trititanium Single Hull plus
foreseeable future. 8cm High Density Armor

CRUSADER
CLASS MEDIUM BOMBER

Originally the response to a requirement issued by the SFMC for a dedicated Assault was considered fundamentally underpowered notwithstanding, Starfleet did so anyways
Transport craft, Crusader ended up transitioning into a premier multi-role craft well adept at during the Dominion War—going on to loose an untold number of these craft in the
the troop transport, ground attack and bomber roles (being officially classified as a process.
Medium Bomber by Starfighter Command).
Two decades after the war’s end, in 2396, the Pulsar class was launched.
Though many saw the introduction and deployment of the Pulsar class Runabout as Succeeding Danube in the majority of front-line applications, it was designed from the keel
a sign that Starfleet was gradually returning to a more militaristic posture, the trends that up to be highly adaptable—permitting the changeout of major systems and components
were influencing and guiding starship and small craft design needed to be taken into as technology evolved. It also corrected many of the Danube’s more notable faults—
context. At the time of the Dominion War, the direction of Starfleet’s ship design remained coming equipped with Quantum Slipstream Propulsion, more powerful weapons and a
dictated by the now infamous ‘multi-mission’ design philosophy that many blamed for the higher capacity deflector shield system.
fleet’s near-annihilation.
To avoid sullying the class’ reputation by having it adapted ‘on the fly’ for more
That philosophy in a larger sense, sought to ensure that a given starship design would military oriented applications (which presented many unknowns not taken into account
be able to undertake and engage in a full spectrum of operations ranging from peaceful during the design process), the ASDB developed a specialized variant, intended
to defensive and offensive. In practice, while the vessels constructed in this vein often specifically for defensive/offensive-oriented applications—codenamed ‘Crusader’.
employed bleeding-edge technologies and displayed advanced designs, they were often
lacking when it came to overall tactical prowess—the Galaxy/Nebula/New Orleans family Aesthetically, changes were minimal—the normal gray/pearlescent thermacoat
being a prime example. being discarded in favor of a darker, charcoal gray thermacoat (minimizing visibility to the
naked eye as well as most sensor systems) as well as external hardpoints that were capable
When it came to small craft, these issues became even more glaring and more often of mounting 8 full size torpedoes or an additional 16 micro torpedoes (though, at the
than not, were not easily rectified—whether due to overall design, sophistication (or lack expense of greater visibility to sensors).
thereof) of technology being employed or some other issue. Such was the case with the
Danube class Runabout. Successfully bridging the gap between small craft and starships, Internally was where most of the substantive changes were made and then, only to
Danube was warp-capable and utilized in a variety of supporting roles, even replacing the ships’s armament and offensive/defensive systems. In a test of just how adaptable
shuttlecraft in certain instances. Crusader was to new technologies, the custom-designed electronic warfare suite from the
Raptor class was modified and incorporated—opening up the possibility of the system’s use
Despite the fact that it quickly became a fleet staple, Danube’s performance in on future small craft designs. The craft’s standard armament was also boosted significantly
certain military applications, such as troop transport and ground attack, was sorely lacking. with the addition of 2 more micro torpedo launchers and a pair of pulse phaser cannons.
The presence of no hull armor, comparatively weak shields and weapons and the fact it Pulsar’s deflector shield system was also extensively modified to provide a higher total
energy capacity—from 67,500 to 73,900 TerraJoules. When combined with the capability
to embark a fully-equipped platoon (60) of troops, Crusader exceeded all expectations.

Entering service in 2398, they have served with the 5th & 7th Bomber wings thus far
and are slated to enter service with the 1st & 3rd Wings within the next 9 months.

Class Crusader
Classification Medium Bomber

Service 2398-

Length 41m
Beam 18m
Class Crusader Height Mass 5m316 metric tons Armament 8 Type VIII Phaser Emitters
Classification Assault Transport (SFMC); Medium 4 Micro Torpedo Launchers
Bomber (Starfighter Command) Compliment 2 (Pilot/Navigator, 2 Pulse Phaser Cannons
Mass 316Weapons
metric tons
Officer) +
Service 2398- 40 Troops (SFMC) Defense Standard Deflector Shield System
Systems total capacity 73,900 TerraJoules
Length 41m Compliment
Beam 18m
1 + 260
(Pilot/Navigator,
passengers Light Duranium/Trititanium Single Hull
Weapons Officer) +
Height 5m 30 Troops (Starfighter
Decks 1 Armament 8 Type VII Phaser
Command) Emitters
4 Micro Torpedo Launchers
2 Pulse Phaser Cannons
8 External Hardpoints (capable of mounting
up to 16 micro or 8 full size torpedoes)
Defense Systems
Standard Deflector Shield System
total capacity 73,900 TerraJoules

Light Duranium/Trititanium Single Hull plus

3cm High Density Armor
AVENGER
CLASS SPACE SUPERIORITY FIGHTER

Intended to succeed the Peregrine class, the Avenger aims to build on the Raptor’s Avenger’s design, was not beholden to such requirements or objectives and subsequently,
success and further enhance Starfighter Command’s ability to project power and exercise featured 6 external hardpoints—2 under each wing, plus 2 forward of the ramscoops—with
absolute control over any battlefield. a total external capacity of 1 full size or 2 micro weapons per hardpoint.

In the later 2390s, a discussion began brewing centered on the quite noticeable age The design process, begun in late 2398, was initially codenamed Valkyrie II—as the
of the two principal attack classes, Valkyrie and Peregrine. Not only was age an issue, but original objective was to create a warp-capable interceptor to replace the original
their lack of warp capability and heavy reliance on carrier ships added a cumbersome Valkyrie (which entered service six decades earlier in 2338). However, Starfleet’s tacit
layer of logistical complexity to their deployments. Whereas Valkyrie was designed from approval of the deployment and use of so-called ‘WMD’s’ (Weapons of Mass Destruction –
the start as an interceptor—with firepower a second-place concern behind speed and of which Tri-Cobalt and Transphasic weapons were considered examples) coupled with a
agility—Peregrine blended all three attributes to create a potent attack platform that general astro-political shift towards asymmetric warfare between the Federation Alliance &
formed the modern backbone of Starfighter Command’s forces. the Typhon Pact, brought renewed relevance to starfighters as tactical tools.

As potent and capable as both were, neither had the range nor the expanded Valkyrie II therefore became Avenger. The original Valkyrie was kept in production
capability needed to achieve complete space supremacy. The development and (due to halt at the end of this year)—still extremely capable as an interceptor—while the
employment of increasingly sophisticated deflector shield systems as well as the gradually focus of Avenger shifted to the area of space superiority. The goal was to produce a
expanded use of hull armor in various forms blunted the effect of micro torpedos—their starfighter that incorporated successful aspects & attributes of both Raptor and Valkyrie
limited yields proving all but ineffective in many instances. Supremacy then, became while still remaining highly capable and easy to construct.
dependent on the ability of starfighters to equip and deploy full-size heavy ordinance.
From a design standpoint, Avenger maintains a roughly similar profile to Valkyrie—a
This ordinance took two forms—conventional and specialized. Conventional slim, angular cockpit positioned forward, tapered wings extending out and slightly
ordinance comprised the proven Photon and Quantum torpedoes used since the early 23rd downward and engines tightly integrated with the hull, contributing to a lower overall
and late 24th centuries respectively. Specialized ordinance took the form of Tri-Cobalt and profile. Unlike Valkyrie though, Avenger’s forward/cockpit section is stretched—
Transphasic torpedoes. The former had been in extremely limited use prior to 2371 due to contributing to a slightly longer length of 19 meters (vs 17 meters for Valkyrie).
their immensely destructive potential, but had entered more widescale use with the advent
of the Dominion War. The latter however, were specially developed anti-Borg weapons first Standard armament consists of 2 Pulse Phaser Cannons (flanking the cockpit), 4 Type
used in 2378. VI Emitters (flanking the warp nacelles—2 forward facing, 2 aft) and 1 Micro Torpedo
launcher (forward). Externally, Avenger is capable of equipping up to 6 full size, 12 micro
weapons or a combination of the two—making it an ideal precision strike craft as well. At
the heart of Avenger is a custom-designed electronic warfare suite that quickly gained
acclaim and soon found its way into the Crusader class Medium Bomber. Special
modifications were made to this suite that increased the overall range and effectiveness of
its ECM/ECCM systems as well as allow its targeting sensors to detect and engage
additional hostiles (owing to its larger external weapons capacity). Borrowing from the
Pulsar class Runabout, Avenger also gained valuable passive scanning, detection and
tracking capabilities).

Defensively, in addition to the aforementioned electronic warfare systems, Avenger

also holds the distinction of being the first small craft to employ a Regenerative Deflector
Shield system. Though not as powerful as its starship-based counterparts, the inclusion of
such a system signifies the value Starfighter Command places on Avenger and continues
Class Avenger Mass 180 metric tons Armament 2 Type V Phaser Cannons
to place on its starfighter force overall. Class Space Superiority/StrikeAvenger
Classification Fighter 4 Type VI Phaser Emitters
Compliment 1 1 Micro-Torpedo Launcher
Classification
Service 2400- Space Superiority/Strike Fighter 6 External Hardpoints (capable of equipping up to 12 full-size or
24 micro-size weapons)
Entering service in 2400, the first examples were delivered to the 3rd Division—forming Length 19m
the new 1st & 3rd Strike Wings along with craft of the Raptor class. By 2405, they had Beam
Service4m
Height
13m
2400-
Defense Systems Regenerative Deflector Shield System
total capacity 92,375 TerraJoules
equipped several more wings—approximately a quarter of which took part in Allied anti- Light Duranium/Tritanium Single Hull plus 6cm Ablative Armor
piracy operations late in that year—seeing the majority of their action against Nausicaan Length 19m
raiders and various Orion Pirate vessels. Beam 13m
Height 4m
Its success in service thus far, combined with its varied armament and heavy
ordinance capabilities have Avenger primed to become Starfighter Command’s next Mass 180 metric tons
great fighter, joining the Peregrine class.

Compliment 1 passengers

Armament 2 Pulse Phaser Cannons

4 Type VI Phaser Emitters
1 Micro Torpedo Launcher
6 External Hardpoints (capable of mounting
up to 12 micro or 6 full size torpedoes)

Defense Systems Regenerative Deflector Shield System

total capacity 92,700 TerraJoules

Light Duranium/Trititanium Single Hull plus

6cm High Density Armor
ARCHANGEL
CLASS ATTACK FIGHTER

The newest starfighter introduced by Starfighter Command, Archangel is a fully warp- further 3 weeks at the Saturn Flight Range for shakedown trials before full scale production
capable replacement for the venerable Valkyrie and Peregrine classes, which after their commenced on 03 March.
decades of faithful service, are due to be retired by the end of the year.
The first 2 squadrons were activated aboard the Command Cruisers Repulse (CC
The introduction of fully warp-capable starfighters, beginning with Omega in 2377 94357) and Olympia (CC 94358), both assigned to Project ‘Full Circle’. A full group,
and continuing with Raptor (2397), Crusader (2398) and Avenger (2400), created operating from the Battleship Charleston (BB 99003) is expected to participate in the
something of a technological gulf in Starfighter Command’s force structure—these Talarian-sponsored Operation Highlander allied wargames exercise later this year (07-14
particular craft not having to exclusively rely on carrier starships for transport to patrol areas July)—the first major test of the class. The results of this exercise are expected to play a part
or battle zones as did Valkyrie & Peregrine. To maintain maximum operational flexibility, it in shaping future deployment strategy, though analysts strongly believe Archangel will see
quickly became clear that a replacement for the two latter classes would eventually be heavy deployment along the Gorn & Kinshaya frontiers.
needed.

As it was replacing two slightly similar, yet ultimately different craft, this new starfighter
would need to be supremely capable in the interceptor, attack, ground assault and
reconnaissence roles—while retaining the ease of construction that had been unparalleled
since the introduction of Valkyrie in 2338.

Codenamed Archangel, the design harkened back to the Thunderbolt class of the
late 22nd century, remaining sleek and rather aeronautically inspired. 13 meters in length,
with a wingspan of 16 meters and displacing 26 metric tons, Archangel retained a roughly
similar profile to Raptor and Avenger—with a tapered, dagger shaped forward section
housing the cockpit, flat angular wings and integrated warp engines. Armament was
comprised of 2 wingtip-mounted pulse phaser cannons and a pair of micro torpedo
launchers housed in the nose, just forward of the cockpit. 6 external hardpoints were also
featured—3 under each wing—giving Archangel the capability to mount 6 full size or 12
micro weapons.

With the design finalized, the prototype took just one week to construct, spending a
Class Archangel Mass 26 metric tons Armament 2 Pulse Phaser Cannons
Classification Attack Fighter 2 Micro Torpedo Launchers
6 External Hardpoints (capable of
Service 2414- Compliment 1 mounting
Defense Systems up to 12 micro or 6 full size
Length 13m torpedoes)
Beam 16m
Height 5m Standard Deflector Shield System
total capacity 70,150 TerraJoules
Bibliography
Type 6
Schematic—Bernd Schneider (Ex-Astris-Scientia) Crusader
Visuals—Daystrom Institute Technical Library Design/Schematic—Galen/Kaden Designs

Type 7 Avenger
Schematic—Bernd Schneider (Ex-Astris-Scientia) Design—G.K. Designs
Visuals—Neutral Zone Starship Database
Daystrom Institute Technical Library Archangel
Design/Ortho Views/Visual—James Trexler (Gallery @ DeviantART)
Type 8
Schematic—Bernd Schneider (Ex-Astris-Scientia)
Visuals—Neutral Zone Starship Database
Daystrom Institute Technical Library
Unknown

Type 9
Schematic—Bernd Schneider (Ex-Astris-Scientia)
Visuals—Daystrom Institute Technical Library
Neutral Zone Starship Database

Type 12
Logos—Kristian “Reverend” Trigwell (Gallery @ Star Trek Minutiae)
Design/Schematics/Description—Gustavo Castillo (Gustavo Castillo’s Designs—GOODSTUFF
2)

Danube
Schematics—Bernd Schneider (Ex-Astris-Scientia)

Pulsar
Design—Galen/Kaden Designs
Visuals—Jack Skieczius (Project Gryphon)

Valkyrie
Design—Warthog Studios/Activision
Visuals—Unknown
’WileyCoyote’ (Model @ BCFiles)

Peregrine
Blueprint—Starship Schematic Database
Visuals—Star Trek: Swiftfire Wiki

Omega
Blueprint—Starship Schematic Database