About: Red Star-class destroyer   Sponge Permalink

An Entity of Type : dbkwik:resource/iy9n5RfxHaRjDjDTh60XKQ==, within Data Space : 134.155.108.49:8890 associated with source dataset(s)

The Red Star-class destroyers were authorized and built in response to the violence of the Jovian Crisis of 2160, but the actual design of the destroyer started in the mid 2150s. At the time, the nascent Koslovic People's Republic possessed a miniscule "space naval service" comprising a few yachts and freighters, with several military ship designs in development. The majority of designs focused on either defensive guard ships or beefed up space yachts, all sharing the characteristics of minimal armament and small size. These were swept aside in late 2158 when Commanders Zhu Qiáng and Ellis Ortega presented their design to the naval proposal board for a two-hundred-and-seventy meter warship with seven missile launchers and six 30mm point defense guns. While quite impressed with the ambition

AttributesValues
rdf:type
rdfs:label
  • Red Star-class destroyer
rdfs:comment
  • The Red Star-class destroyers were authorized and built in response to the violence of the Jovian Crisis of 2160, but the actual design of the destroyer started in the mid 2150s. At the time, the nascent Koslovic People's Republic possessed a miniscule "space naval service" comprising a few yachts and freighters, with several military ship designs in development. The majority of designs focused on either defensive guard ships or beefed up space yachts, all sharing the characteristics of minimal armament and small size. These were swept aside in late 2158 when Commanders Zhu Qiáng and Ellis Ortega presented their design to the naval proposal board for a two-hundred-and-seventy meter warship with seven missile launchers and six 30mm point defense guns. While quite impressed with the ambition
Era
dcterms:subject
build range
  • 2160(xsd:integer)
dbkwik:halo-fanon/...iPageUsesTemplate
dbkwik:halofanon/p...iPageUsesTemplate
Operators
Ship type
Name
  • Red Star-class destroyer
Hide header
  • yes
Ship armament
  • 4(xsd:integer)
  • 5(xsd:integer)
  • 6(xsd:integer)
  • Ardent-type:
  • Aware-type:
Subclasses
  • [[#Ardent-type
Ship complement
  • 9(xsd:integer)
  • 10(xsd:integer)
  • 14(xsd:integer)
Total ships completed
  • 27(xsd:integer)
In commission range
  • 2161(xsd:integer)
Builders
  • KPR Shipyards
Class before
Class after
Ship length
  • 233.0
  • 239.0
  • 237.0
abstract
  • The Red Star-class destroyers were authorized and built in response to the violence of the Jovian Crisis of 2160, but the actual design of the destroyer started in the mid 2150s. At the time, the nascent Koslovic People's Republic possessed a miniscule "space naval service" comprising a few yachts and freighters, with several military ship designs in development. The majority of designs focused on either defensive guard ships or beefed up space yachts, all sharing the characteristics of minimal armament and small size. These were swept aside in late 2158 when Commanders Zhu Qiáng and Ellis Ortega presented their design to the naval proposal board for a two-hundred-and-seventy meter warship with seven missile launchers and six 30mm point defense guns. While quite impressed with the ambition of the design, the review board reduced the armament significantly, citing inadequate supplies of missiles and equipment, and shortened the vessel by forty meters for similar reasons. Nevertheless, the revised design more than satisfied the board and the navy, and received the class name of "Red Star" in 2159.
is Class of
is Ship class of
is Class before of
is Class after of
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software