FANDOM


Cannons

FIRE!

This article should be Gamified to fit within the style of SWGames

Please follow the guidelines in the Manual of Style and How to edit a page.

GrievousactionBFII

More... More... MORE!

It is requested that this article, or a section of this article, be expanded.

See the request on the listing or on this article's talk page. Once the improvements have been completed, you may remove this notice and the page's listing.

TIE Hunter
TIE Hunter
Production information
Manufacturer

Sienar Fleet Systems

Product line

TIE series

Model

Twin Ion Engine Hunter

Class

Starfighter

Technical specifications
Length

10 meters (approximate)

Hyperdrive rating

Equipped

Armament
Crew

1 (Pilot)

Usage
Role(s)

Space superiority fighter

Era(s)

Rebellion era

Affiliation

Galactic Empire

  [Source]

The TIE Hunter was an Imperial fighter piloted originally by Imperial pilots. The ship is mainly a cross between a Rebel X-wing and a TIE Interceptor. The TIE Hunter is faster and deadlier than any other TIE ship. The TIE Hunter is equipped with blasters, lock-on Proton Torpedoes, and two Ion cannons.

Mission HistoryEdit

In the first mission, "Deception at Destrillion", Wedge Antilles was sent by General Crix Madine to find an Imperial Research Facility. While traveling in his A-wing through the energy tunnels, Wedge relayed this message to Madine: "Picking up fighters on my scope. They're not like anything I've seen before!", Madine's reply: "Those must be the new TIE Hunters. Be careful, they're very deadly!"

In the mission known as "Fondor Shipyard Assault", the Rebels seem to have captured three TIE Hunters and used them to destroy cloaking devices on a Super Star Destroyer named Fondor.

AppearancesEdit

MFalcon This article is a stub about a type of ship or starfighter. You can help SWGames by expanding it.

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.