Technology / Fang-Class Fighter

Field Record: TEC-PFT-032Archive Node: Space PiratesClearance: Science Team / Level 04Review Status: Hostile Vehicle Record Converted
Name
Fang-Class Fighter
Legacy Designation
Pirate Fighter
Item Class
Space Pirate light fighter / strike craft
Manufacturer / Origin
Space Pirate fleet and planetary-defense workshops
Primary Role
Interception, strafing, pursuit, escort disruption, and swarm pressure
Operating Theater
G.F.S. Olympus attack lanes, Norion airspace, Pirate Homeworld defenses, and Phaaze approach battles
Field Access
Hostile craft; intact cockpit capture requires fleet security and ordnance isolation
Summary
Fang-Class Fighter is the archive class name for a fast Pirate strike craft documented during the Phazon War. The older Pirate Fighter label remains preserved as a legacy field term, but the role is clear: screen larger actions, harass Federation assets, and keep defenders under constant movement pressure.
Operational Notes
The craft appears across several major battle zones, including the G.F.S. Olympus, Norion, the Pirate Homeworld, and Phaaze. That spread suggests a common fighter pattern or family rather than a single local prototype.
Space Pirate technology archive image of Fang-Class Fighter strike craft showing hostile vehicle scan profile
Survey StatusHostile Fighter Record
Behavior IndexInterceptor / Swarm Asset
Science ValueFleet Doctrine
Field AccessMilitary Salvage Only

Distinct Features

The Fang-Class Fighter is defined by predatory speed and formation pressure. Earlier Federation records used Pirate Fighter as a field label because the craft was documented through combat sightings rather than a clean captured registry. That uncertainty remains part of the record, since misreading a Pirate chassis can hide useful fleet-pattern evidence.

Its visible identity comes from speed, small profile, and aggressive attack routing. A fighter of this type does not need heavy armor if it can cross a firing lane, break pursuit, and return from another angle before defenders reset. The craft is therefore best identified by movement, weapon timing, and formation behavior as much as by hull silhouette.

The strongest evidence places the type in several Phazon War theaters. Sightings around the G.F.S. Olympus, Norion, the Pirate Homeworld, and Phaaze point to a combat platform that could operate with shipboard raiding forces and planetary defense screens. That range makes the Fang a useful marker for Pirate logistics across the campaign.

Operational Profile

Fang-Class Fighters operate as pressure tools for larger attacks. They strafe open lanes, chase exposed craft, and force defenders to split fire between fast targets and the main assault. In a fleet engagement, even a fragile fighter becomes dangerous when it decides who can safely move.

The craft should be expected wherever Pirate forces need quick air or space denial. Around Norion or the Olympus, that means sudden runs against hangars, turrets, marine positions, and exposed service routes. Around Phaaze or the Pirate Homeworld, it means screening corrupted fleet assets and buying time for heavier systems to complete their work.

Captured wreckage should be approached as hostile even after the pilot is dead. Ammunition cells, jamming modules, and cockpit failsafes may remain armed to destroy evidence or injure boarding teams. A science team should wait for fleet technicians before treating any intact avionics as recoverable data.

Mission Relevance

The Fang-Class Fighter gives a mission designer a way to make open space feel dangerous without introducing a capital ship. It can harass a landing party, pin an extraction craft, or turn a repair task into a timed air-defense problem. Its threat comes from speed and repetition rather than a single overwhelming shot.

For field play, the Fang works best in pairs or small groups. One craft can draw sensor locks while another hits a turret, bridge, or transport bay. That pattern makes players think about cover, timing, and protecting support assets instead of simply trading fire.

As an archive subject, the entry also protects naming discipline. It acknowledges the older field label while giving teams a cleaner in-universe class name for the observed craft. Future updates can refine the record if a production marking, scan log, or official class term is recovered.

=End Of File-

Return To Technology Index