STAR ARMY

Sci-fi roleplaying and worldbuilding community

User Tools

Site Tools

Trace: • Sophie Trang • Pegasus-Class Starship: Yume no Kaseki (Fossil of Dreams) • Ake • SSS Bisen Lighthouse Deployment • Magnusson Yuu • Oxen Multipurpose Mecha • Elysian Characters • Takara I
faction:nepleslia:starship_classes:sword_class_frigate

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Last revisionBoth sides next revision
faction:nepleslia:starship_classes:sword_class_frigate [2018/12/10 08:00] – [Weapons Systems] frostjaegerfaction:nepleslia:starship_classes:sword_class_frigate [2019/04/03 11:21] – ↷ Links adapted because of a move operation wes
Line 32: Line 32:
 Noting the lack of a dedicated anti-starfighter escort in the [[faction:nepleslia:military:nepleslian_star_navy|Nepleslian Space Navy]], [[corp:nepleslian_arms_and_munitions|NAM engineers]] designed and built a frigate-sized vessel to fulfill that role.  However, it became clear that if the frigates were expected to be accompanying capital warships and heavier escorts, they would also need to have the ability to threaten enemy warships. Noting the lack of a dedicated anti-starfighter escort in the [[faction:nepleslia:military:nepleslian_star_navy|Nepleslian Space Navy]], [[corp:nepleslian_arms_and_munitions|NAM engineers]] designed and built a frigate-sized vessel to fulfill that role.  However, it became clear that if the frigates were expected to be accompanying capital warships and heavier escorts, they would also need to have the ability to threaten enemy warships.
  
-Planning began in early[[calendar:ye_32]] and the first batch of two prototypes were soon delivered for flight testing.  Despite some teething issues, core systems were deemed to perform to specification and that the vessel was, overall, quite sturdy.  The second batch of three prototypes were delivered in mid [[calendar:ye_33]] with the full spectrum of systems and were used as testing grounds for systems integration and combat simulation.  One concern from computerized testing, which was confirmed with the destruction of Prototype 2C as a target for live weapons, was the poor amount of structural reinforcement to withstand powerful hits from anti-starship weapons.  To compensate a third batch of prototypes were made with thicker bulkheads, redundant supports and beams and the thick armor plating around the flanks of the ship.+Planning began in early[[timeline:ye_32]] and the first batch of two prototypes were soon delivered for flight testing.  Despite some teething issues, core systems were deemed to perform to specification and that the vessel was, overall, quite sturdy.  The second batch of three prototypes were delivered in mid [[timeline:ye_33]] with the full spectrum of systems and were used as testing grounds for systems integration and combat simulation.  One concern from computerized testing, which was confirmed with the destruction of Prototype 2C as a target for live weapons, was the poor amount of structural reinforcement to withstand powerful hits from anti-starship weapons.  To compensate a third batch of prototypes were made with thicker bulkheads, redundant supports and beams and the thick armor plating around the flanks of the ship.
  
 These late additions to the design were to prevent the penetration of the ship's magazine, containing the [[faction:nepleslia:weapons:curbstomper_long-ranged_missile_system|"Curbstomper" Long-Ranged Missile System]], or the engine compartment by enemy weaponry.  Due to the small size of the ship, there is only one central magazine from which ammunition for the missile systems must be drawn.  Its loss would cripple the ship's ability to remain in the battle, assuming it had not been destroyed by the simultaneous explosion of all of remaining warheads in the magazine.  Likewise, the need to protect the engine compartment was two fold.  Without the engines to give the Sword its great speed, the frigate would be an easy target for larger, more powerful warships.  Secondly, it was added for aesthetic reasons and symmetry. These late additions to the design were to prevent the penetration of the ship's magazine, containing the [[faction:nepleslia:weapons:curbstomper_long-ranged_missile_system|"Curbstomper" Long-Ranged Missile System]], or the engine compartment by enemy weaponry.  Due to the small size of the ship, there is only one central magazine from which ammunition for the missile systems must be drawn.  Its loss would cripple the ship's ability to remain in the battle, assuming it had not been destroyed by the simultaneous explosion of all of remaining warheads in the magazine.  Likewise, the need to protect the engine compartment was two fold.  Without the engines to give the Sword its great speed, the frigate would be an easy target for larger, more powerful warships.  Secondly, it was added for aesthetic reasons and symmetry.
  
-In late [[calendar:ye_33]], the Sword class was ready for full scale production.  It saw limited action with the 4th Fleet as an escort during [[faction:nepleslia:history:rok_veru_offensive]].  It was removed from front-line service and replaced by the more durable [[faction:nepleslia:starship_classes:atlas_destroyer]] in early [[calendar:ye 34]].  Sword frigates were retained as system defense and patrol craft.  Squadrons of them were being used to secure Nepleslia's colonies and borders in [[calendar:ye 35]].+In late [[timeline:ye_33]], the Sword class was ready for full scale production.  It saw limited action with the 4th Fleet as an escort during [[faction:nepleslia:history:rok_veru_offensive]].  It was removed from front-line service and replaced by the more durable [[faction:nepleslia:starship_classes:atlas_destroyer]] in early [[timeline:ye_34]].  Sword frigates were retained as system defense and patrol craft.  Squadrons of them were being used to secure Nepleslia's colonies and borders in [[timeline:ye_35]].
  
 ===== Statistics and Performance ===== ===== Statistics and Performance =====

Page Tools

Content copyright StarArmy.com and/or individual contributors and used under license. Star Army is a registered trademark.
Terms of Service - Privacy Policy