This HTML5 document contains 6 embedded RDF statements represented using HTML+Microdata notation.

The embedded RDF content will be recognized by any processor of HTML5 Microdata.

Subject Item

n2:

rdfs:label

CMS Turbulent

rdfs:comment

CMS Turbulent (CFC-04) is the fourth example of the Hurricane-class carrier, launched after considerable delays and interruptions in 9 ABY. The capital-scale vessel is significantly different from the rest of its class due to a myriad of influences, but while it has often been referred to as a separate class, it is still classified as a Hurricane-type.

dcterms:subject

n7:

n4:wikiPageUsesTemplate

n5: n9:

n8:abstract

CMS Turbulent (CFC-04) is the fourth example of the Hurricane-class carrier, launched after considerable delays and interruptions in 9 ABY. The capital-scale vessel is significantly different from the rest of its class due to a myriad of influences, but while it has often been referred to as a separate class, it is still classified as a Hurricane-type. From 9 ABY to 15 ABY, it was the primary planetary-operations (the Caspian Democratic Union refrains from using the term "assault") vessel in the Caspian Navy, equipped with smaller craft, machinery, and supplies to support actions or installations on any sort of terrestrial body. The Navy and Marines employed Turbulent as a coordinator and platform for close operations support while other vessels — Ushton-class LHC's, Leyden-class LPD's, etc. — perform the actual interaction with the landing and insertion zones. The much more modern CMS Tonare has since become the primary vessel in the Navy's arsenal for this role, but after a refit in 16 ABY, Turbulent will continue to perform in this valuable capacity alongside other elements of the fleet.