FANDOM


Tiehd
TIE/hd advanced automated starfighter
Production information
Manufacturer
Product line

Mustafarian TIE Series

Model

Twin Ion Engine Hunter Drone advanced automated starfighter

Class

Advanced Automated Starfighter

Cost

200,000 credits

Technical specifications
Length

9.6m

MGLT

S-Foils Open

  • 110

S-Foils Closed

  • 118
Maximum speed (atmosphere)

1,250 km/h

Engine unit(s)

Twin Ion Engine

Hyperdrive rating

Class 1.0

Shielding

Novaldex deflector shields (100 SBD)

Hull

Titanium alloy hull (20 RU)

Armament
Crew

Cybot Galactica Ace-6 droid brain (1)

Usage
Role(s)

Space superiority fighter

The TIE/hd advanced automated starfighter was originally a prototype automated starfighter for the Empire, researched at Mustafar. The project started with a new TIE Hunter fighter, which, although it was in enemy hands for the feat, was seen as capable of doing amazing things, such as destroy an Executor-class Star Dreadnought that was in construction at Fondor. This prompted the Empire to make use of the fighter against their enemy, in numbers so large that they outnumbered the available TIE Pilots, in order to overwhelm their opponent. So, they decided to make use of the Droid Foundries on the planet of Mustafar to create Droid Brains for the starships. Unfortunately for the Empire, halfway into the project, the Emperor and Darth Vader died at Endor, prompting a bloody revolution on Mustafar, in which the Empire lost control of the planet, as well as the project. The project then, fell into the hands of the Mustafarian Merchants Alliance, of which contained some Mustafarians who worked on the project itself. Needless to say, the Mustafarian Merchants Alliance took control of the project, and finished it, planning to use the fighter to fill the role of a space superiority fighter.

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.