Fandom

Halo Fanon

Ashforth-class Frigate

11,434pages on
this wiki
Add New Page
Talk0 Share
Avatar2era
Terminal This article, Ashforth-class Frigate, was written by Rozh. Please do not edit this fiction without the writer's permission.
Ashforth1
Ashforth class Frigate
Production information
Manufacturer

NaTech Industries

Class

Ashforth

Type

Frigate

Technical specifications
Armor

Titanium-A battleplate

Chronological and affiliation
Era
Affiliation

UNSCnew-1 UNSC Navy (UND)
Haverson3 Haverson Defense

  [Source]

The Ashforth-class Frigate was a light-tonnage warship employed by United Nations Space Command forces during and after the Human-Covenant War. Often referred to as expensive cannon fodder, ships of the line were highly vulnerable to hostile space forces, also they proved to be much more efficient when supporting forces on the ground. The first ship of the class, the UNSC Ashforth, was launched alongside six sister vessels in 2529, and the final vessels of the class were either reallocated or scrapped in the early to mid-2580's.

Notably, in 2588, private security contractor Haverson Defense purchased two Ashforth frigates, sans various operating systems, and modified them into blockade runners.



Space-faring vessels of the UNSC Navy
Fleet vessels

Baku-classReach-classTitanic-classTrojan-classValkyrie-class

Capital vessels

Black Wolf-classCeltic-classKing-classMountaineer-classSemaj-classSeminole-classXerxes-classYamato-class

Escort vessels

Aias-classAshforth-classDrako-classDust-classJohn Paul Jones-classMammoth-classRetarius-classSan Diego-classVenus-class

Direct support vessels

Caravel-classIo-classHindu Kush-classOliver Hazard Perry-classThor-classVALS-class

Auxiliary vessels

Alaska-classBarcelona-classBorneo-classGriffin-classHarvest-classMadrid-classMars-classMonterrey-classNiagara-class

Ad blocker interference detected!


Wikia is a free-to-use site that makes money from advertising. We have a modified experience for viewers using ad blockers

Wikia is not accessible if you’ve made further modifications. Remove the custom ad blocker rule(s) and the page will load as expected.