
TASK FORCE 22
Introduction
In the year 3172, TF 22 deployed from the Earth Defense Fleet
to the Storm Zone to reinforce the beleaguered units of the Navy of the Terran Satellite
Charter fighting against the Dindrenzi invasion. This fleet was constructed
by the orbital shipyards of the United Americas. Specifically, they were
funded and manned by the former United States, whose territory still has a
dominant influence within the United American federation. As such, the ships
follow the traditional naming schemes and organizational schemes of the
former United States Navy.
Scheme
TF 22 uses a simple scheme that allows for the easy identification of
different ships within the formation. Dark blue is used as an accent color,
and is the overall fleet color. Each squadron has an identification marking
on the port engine housing (in the case of ships that are in squadrons of
one ship, such as the battleship, the marking on the Port engine is the
ship's logo). The squadron leader will have a white stripe on it's bow to
identify it as such, while each ship's name (or hull number, in the case of
Small ships) appears on the Starboard engine.
Ships
|
CSS INDIANA |
The CSS INDIANA, a Razorthorn-Class battleship, was laid down as part of the emergency construction program launched as part of the Commonwealth's response to the Terran War. However, she was not commissioned until the year 3675, too late to see action against the Dindrenzi. She spent the next decade serving as part of the defense fleet that patrolled the Commonwealth-Dindrenzi border following the armistice, but was de-activated in the year 3686 as part of a defense draw-down and placed into the Earth Orbital Reserve Fleet. With the coming of the Alliance of Kurak and the corresponding expansion of the NTSC, the INDIANA was re-activated and entered the yard to have the latest advancements in shield and sensor technology installed. She was officially returned to active service in the year 3717 and made the flagship of Task Force 22, which was initially assigned to the defense of Earth. |
|
CSS HORNET |
The CSS HORNET is a Zenith-class carrier, tasked with providing TF 22 Wing support. The Zenith design is relatively new, the first ship of the class having been commissioned in 3714. In fact, TF 22 is the HORNET's first assignment, as she is fresh from her builder's trials. Although she carries fewer Wings than previous designs, she does have a strong direct combat capability, heavier armor, and the shielding capacity of a battleship. Together, they make the HORNET a powerful addition to TF 22. |
|
CSS CHICAGO, CSS HOUSTON, CSS SAN FRANCISCO |
The CSS HOUSTON, CSS SAN FRANCISCO, and CSS CHICAGO form Cruiser Squadron 15 (CS 15), and operationally make up Task Group 22.2 (TG 22.2). All three ships are Sentinel-class cruisers, a proven design that has been in use for over 100 years. Thanks to constant upgrades and refits, the Sentinel has remained a vital part of the NTSC fleet. All three ships of Squadron 15 are relatively new, having all been commissioned in the last 10 years. They are all Flight IVa ships, which was the first version of the class to be built with shield technology. Older flights have had their shields back-fitted, and have suffered reliability problems as a result of the extra strain put on their power distribution systems. Operationally, CS 15 was briefly assigned patrol duties along the trade routes between the major planets in the Hub, which is generally considered light duty suitable to new ships still in the shakedown phase. They were all re-assigned to TF 22 upon its stand-up in 3717. |
|
Pilgrim-class
Frigates Frigate Squadrons 11 and 16 (TG 22.4 and TG 22.5 respectively) provide the frigate support to the task force. Comprised of 3 Pilgrim-class frigates each, these ships perform numerous duties including scouting, screening, and fire support. The Pilgrim-class, like the Zenith-class carriers, are a relatively new design that benefits from the exchange of technology with the Kurchas Tribes. Despite some initial teething troubles, the class has matured into a robust design that compares favorably with other ships of its type. FS 11 was part of TF 22 from its founding, while FS 16 was attached to the task force just prior to its reassignment to the Storm Zone. |
|
|
|
|
Andy "Ruckdog" Rucker