Click here for Wookieepedia's article on the Canon version of this subject.  This article covers the Legends version of this subject. 
For other uses, see TIE/D.

"Imperial High Command decided that defender pilots would only be selected from TIE interceptor pilots who had flown at least twenty combat missions and survived. We're either the best pilots in the Imperial fleet or the luckiest."
Rexler Brath[7]

The TIE/D Defender, commonly known as the TIE Defender or T/D, was a high-performance TIE Series starfighter developed for the Imperial Navy by Sienar Fleet Systems in a project overseen by Grand Admiral Demetrius Zaarin shortly before the Battle of Endor. Representing a shift in starfighter design from previous TIE models, the ship featured a hyperdrive as well as deflector shields to allow it to operate independently of Imperial capital ships. The ship's speed and agility, combined with its arsenal of four laser cannons, two ion cannons, two warhead launchers, and an optional tractor beam projector, made it arguably the most advanced starfighter available at the time.

After Zaarin's failed coup against Emperor Palpatine, the renegade admiral attempted to gain control of the TIE Defender technology to give his forces a technological advantage over the Empire. The advanced starfighter also attracted the attention of other factions, including the Rebel Alliance and pirate groups. Imperial forces under the command of Grand Admiral Thrawn were ultimately able to prevent the spread of the technology and the starfighter played a major role in Thrawn's successful campaign against Zaarin.

Beyond the Zaarin campaign, the TIE Defender's high cost, together with political factors, kept it from achieving widespread use in the Empire and units were assigned only to the most elite pilots. The fighters participated in several other engagements during the Imperial era, including the Battle of Mygeeto and the Battle of Endor. Following the death of Emperor Palpatine at Endor, the TIE Defender continued to see limited use by Imperial forces. TIE Defenders saw action during Shadowspawn's campaign against the New Republic in 5 ABY and were used by the Republic's Rogue Squadron during a brief alliance with former Director of Imperial Intelligence Ysanne Isard against Prince-Admiral Delak Krennel's Ciutric Hegemony in 9 ABY. The fighters participated in multiple battles during the Yuuzhan Vong War and continued to be used by the Imperial Remnant until at least 44 ABY.


"A logical advance for Imperial fighter design."
―Imperial propaganda[14]

The high success rate of more advanced Rebel starfighters against standard Imperial TIE Fighters resulted in a mounting cost of replacing destroyed fighters. That, combined with the realization that the inclusion of a hyperdrive would allow the fleet to be more flexible, caused the Imperial Navy to rethink its doctrine of using swarms of cheap craft instead of fewer high-quality ones, leading to the introduction of the TIE Advanced x1[15] and its successor, the TIE Avenger.[16] The TIE/D Defender,[1] commonly known as the TIE Defender or T/D,[2] was touted as the next "logical advance" of the TIE Series—a starfighter that was fast, well-armed, and capable of hyperspace travel.[4]

Sienar Fleet Systems followed specific Imperial instruction in developing the TIE Defender,[4] among them the requirement that the fighter would exceed the mission capability of a flight group of four standard TIE Fighters.[17] As such, it was equipped with a series of innovations over previous models.[15] The practice of designing craft to explicit consumer specifications was one that Sienar would continue with the later Scimitar assault bomber[18] and Aleph-class starfighter.[19] The TIE Defender was 9.2 meters long.[6]

Pilot module[]

"Energy management will be a bit more complex, but the Defender has much more powerful energy systems. This will allow you to maintain most systems at maximum recharge and still retain a high speed."
Imperial briefing officer — (audio) Listen (file info)[2]

A TIE Defender's pilot module

The pilot module was similar to those found in other TIE series fighters, with a ball cockpit and a hatch on the top for entry and egress.[15] The module had room for a single pilot,[1] 65 kilograms of cargo[9] and consumables for up to one week.[10] Like previous TIE models, the TIE Defender lacked life support systems and pilots were required to wear the standard sealed TIE pilot flight suit.[17]

In a departure from the design of previous TIE models, which typically had two parallel wings to either side of the pilot module,[2] the TIE Defender had three quadanium steel solar array wings[20] mounted around an aft section. The rear superstructure contained an I-s4d solar ionization reactor to store and convert solar energy collected from the wing panels.[17] The distinctive triple-wing shape of the TIE Defender led Corran Horn to dub them "trips,"[21] and the nickname was also adopted by other Rebel pilots.[17] The wings themselves appeared similar to those found on the TIE Interceptor and TIE Avenger; unlike on its predecessors, the wings on the TIE Defender were angled out instead of in.[21] The inclusion of a third wing provided additional solar power to increase the ship's range[15] and the ship's energy management system was designed to allow weapons and shields to be charged with minimum loss of power to the propulsion system.[2]

One disadvantage of the design was an aft blind spot which could potentially be exploited by enemy fighters maneuverable enough to get behind the Defender[22] and which was the cause of some frustration among pilots.[15]


"With its hyperdrive capability, high maneuverability, the quickest acceleration and fastest sublight speed yet achieved, you have the most powerful starfighter in the galaxy!"
―Imperial briefing officer — (audio) Listen (file info)[2]

The TIE Defender was one of the fastest starfighters in use during the Galactic Civil War.[4] Although it was based on the standard twin ion engine design, it was upgraded to the entirely new[15] P-sz9.7 twin ion engine, which was rated at 230 KTU[1] and allowed it a maximum acceleration of 4,220 G[7] or 21 MGLT/s and a top speed of 144 MGLT[8] or 1,680 km/h in an atmosphere—almost 40 percent faster than a standard TIE Fighter.[7] With tractor beam recharge power redirected to the engines, the top speed could be increased to 180 MGLT.[8] In addition to the main thrusters located in the aft section,[15] the Defender's triple wing design allowed for three arrays of maneuvering jets[6]—which gave it a maneuverability rating of 110 DPF[8]—and it featured an advanced F-s5x flight avionics system to process the pilot's instructions. When combined, these systems made the ship not only faster, but more agile than any other starfighter in Imperial service[6] and capable of matching the fastest starfighters in the Alliance Fleet.[17]

The TIE Defender also featured a hyperdrive which allowed it to operate independently of capital ships.[4] Testing of the original prototype indicated the need for a more powerful hyperdrive[23] and production models included a class 2[7] ND9 hyperdrive motivator[1] modified from the version developed for the TIE Avenger.[11] The ship had a Sienar N-s6 Navcon navigation computer[1] with a ten-jump memory.[5]


"You'll find the Sienar Fleet Systems TIE Defender is the fastest, best-equipped starfighter in the galaxy."
―An Imperial flight instructor[21]

One of the TIE Defender's quadanium steel solar array wings

The TIE Defender's weapons systems were designed to allow it to engage multiple enemy fighters[4] as well as the armed freighters frequently used by the Alliance.[9] It carried a formidable array of weaponry; in standard configuration, it had four L-s9.3 laser cannons mounted on the two lower wings and two NK-3 ion cannons mounted on the upper wing. The laser and ion cannons could be set to fire separately or, if concentrated power was required, to fire-linked in either pairs or quartets.[7] The ion cannons could even be fired simultaneously with the laser cannons.[9] Two targeting sensors were located between each pair of cannons to provide the pilot with a constant stream of targeting information.[15]

The ship also featured two M-g-2 general-purpose warhead launchers on the bottom of the pilot module,[6] each of which could be equipped with a standard load of three proton torpedoes or four concussion missiles. Depending on the mission profile, the ship could be fitted with alternative warheads such as proton rockets, proton bombs, or magnetic pulse warheads.[11] The inclusion of warhead launchers in the design was considered audacious by some members of the design team.[15]

The small tractor beam projector developed for the TIE Avenger could be easily fitted to the Defender.[2] The tractor beam had limited range and could only be used for a short time before stopping to recharge, but it allowed the pilot to temporarily inhibit the mobility of enemy fighters, making it easier to target them with the ship's other weapon systems.[24] Models produced by Ysanne Isard's Defender production facility regularly carried such tractor beams, and the technology found other uses, such as allowing TIE Defenders to tow damaged starfighters until they could achieve the required velocity to enter hyperspace. Corran Horn discovered that by using the beam to target a large object, he could effectively use it as an anchor, allowing the TIE Defender to achieve a tighter turning circle.[21]

The ship's defenses were provided by a pair of forward and rear projecting Novaldex deflector shield generators—another advantage over standard TIE models.[6] The shields were designed to recharge more rapidly than in previous Imperial fighters[2] and were nearly as powerful as those found on capital ships,[25] with a total rating of 100 SBD.[1] The fighters were not equipped with particle shields, instead relying on the reinforced titanium hull to absorb impacts from matter.[25] Its hull and wings were the strongest of any TIE series starfighter[17] and were rated at 14 RU.[8]



Interior view of a TIE Defender cockpit

As with other TIE series fighters, the TIE Defender used a wheel and yoke control system. Pulling back would cause the ship to climb, pushing forward would cause it to dive, and the ship could be made to bank and turn by twisting the controls. Grips on either side had the weapons trigger switches, and an array of buttons and switches in the middle controlled other functions, including throttle, weapons selection, and target acquisition. Manipulating rudder pedals caused maneuvering planes to expand or contract to angle engine thrust and quickly alter the ship's trajectory. The ship featured an auto-landing function to plot entry vector and landing speed, although the pilot could retain manual control if they preferred. While not in use, the ship could be left in a password-controlled standby mode to prevent unauthorized use.[21]

Various display panels inside the cockpit allowed the pilot to monitor the ship's systems and the surrounding area. The main Combat Multi-view Display displayed sensor data on targeted ships while additional monitors displayed short-range sensor contacts. Additional panels displayed the remaining charge of weapons, shields, and tractor beam systems, as well as current warhead load and power usage. A chronometer was used to display the mission time[2] or during hyperspace travel to countdown to reversion to realspace.[21] A heads-up display assisted the pilot in aiming the ship's weapons and displayed data from the ship's threat warning system.[2] Like other TIE series starfighters, TIE Defenders were mounted on racks in the hangar when carried aboard a capital ship.[2][14]


TIEdefender schem

TIE Defender schematics

The TIE Defender was, in many ways, far superior to any other starfighter of the time, capable of outperforming the majority of Rebel starfighters with its combination of firepower, speed, and maneuverability.[15] However, its sophisticated features had two major implications. First, the inclusion of the hyperdrive, shields, and reinforced armor made the ship heavier than any of its predecessors—a fact which made its speed and maneuverability all the more impressive.[15] Second, and more importantly, the ship was very expensive, with each unit costing 300,000 credits—more than five times the cost of a standard TIE fighter[4]—or 80,000 credits used.[5] High maintenance and training costs added further to the expense of the fighters.[10]


"TIE Defender, standing by."
―A TIE Defender pilot[26]

The TIE Defender was designed to serve as a multi-role starfighter, capable and durable enough to take on a variety of missions.[10] Standard Imperial doctrine recommended that TIE Defenders operate in flight groups of four; however, Imperial commanders took advantage of the starfighter's superior abilities to customize mission forces on a case-by-case basis.[4] Defender pilots often found themselves occupying mission roles previously held by older fighters such as TIE Interceptors and Assault Gunboats.[11]

TIEdefender negvv

A TIE Defender

The TIE Defender's weaponry and deflector shields made it an ideal space superiority fighter, capable of engaging multiple enemies at once.[4] The craft possessed impressive speed promoting its function as a superior interceptor, capable of eliminating incoming starfighters before they posed a threat to Imperial capital ships. Pound for pound, each TIE Defender matched or exceeded all Rebel starfighters in speed, armament, defenses, and maneuverability, proving a worthy adversary against even Imperial forces.[1] Their effectiveness against Rebel forces earned them the nickname "X-wing Killers" among TIE Defender pilots and crew.[10]

Their hyperdrives allowed TIE Defenders to conduct patrols across large areas of space without support from capital ships.[4] The Defender's versatility allowed a large degree of flexibility in its use, as even a single craft could prove formidable,[6] able to outrun or outgun enemy fighters. While on reconnaissance missions, Defenders could also bring heavy ordnance to bear on enemy capital ships. Upon the discovery of Grand Admiral Zaarin's plot against Emperor Palpatine, the Sith Lord Darth Vader employed the TIE Defender's abilities in that role, breaking through Zaarin's lines to reach the planet Coruscant. Lord Vader's flight group destroyed the Immobilizer 418 cruiser Harpago, which was attempting to block his imperative voyage.[2]

The TIE Defender's ion cannons, paired with the ability to carry multiple warhead types, allowed it to function as an effective light bomber or assault fighter.[27] TIE Defenders often assumed missions to disable or destroy enemy installations or capital ships, at times by a single flight group or with only Gamma-class ATR-6 assault transports as support.[11] Defender squadrons could combine their firepower to eliminate a target as large as Alliance Space Stations, while still covering the starfighter interception role.[28]


"Now, some good news for you! You have been selected to receive advanced combat training in the new TIE Defender. Report to the Combat Chamber…"
―Imperial briefing officer[2]

TIE Defender prior to launch

Opportunities to train on the TIE Defender were limited.[7] Only high-ranking ace TIE Interceptor pilots[10] who had survived at least twenty combat missions[7] and whose loyalty to the Empire was undisputed were selected, ensuring that only the best pilots flew the advanced starfighter.[10] During the Galactic Civil War, Imperial pilots were required to gain a training certificate by flying the TIE Defender through an enclosed training course before proceeding to simulated combat missions. The training course consisted of a cylindrical loop containing targets and obstacles for pilots to traverse. Defender pilots raced against the clock to navigate the course, destroying targets when at all possible to gain bonus time.[2] Having received a training certificate, Defender pilots could move onto the combat scenarios, some of which were based on historical sorties, designed to familiarize the pilot with the controls and handling of the starfighter before they entered actual combat.[1] If the pilot successfully completed all four training missions, they received the gold TIE Defender combat medallion.[2]

By the later years of the Empire, less rigid training regimes were in use. When Rogue Squadron trained on the TIE Defender against Imperial forces commanded by Ysanne Isard, they engaged the Imperials in a series of mock battles including a recreation of an Imperial attack on Rogue Squadron's former base at Yag-prime.[21]

Combat scenarios[]

The first combat training exercise tested the pilot's ability to dogfight against a variety of Rebel starfighters and allowed them to customize the difficulty of the mission by controlling the number and skill of opponents, to a maximum of 250 potential kills. For a greater challenge, the pilot could choose to face enemy TIE Defenders. Defender pilots began the simulation stationary, surrounded by five cargo containers. Upon inspection of named containers, for example "Y-wing," individual starfighters entered the system at increasing difficulties, five in all. Defender pilots could increase the challenge by attacking the container, sending in all difficulty levels at one time. In the event that the pilot could not handle the increased demands of the mission, destroying the container resulted in the spacecraft derived from the inspection entering hyperspace. Another control level installed consisted of enemy fighters responding to the trainee's orders; pilots could instruct enemy fighters to wait or head for home in the event the challenge grew too great.[2]

In order to test the pilot's ability to make effective use of a tractor beam, the second combat exercise challenged them to prevent the escape of a Rebel spy from a salvage yard near Venzeiia 2 Prime. In a recreation of a mission led by the Imperial-class Star Destroyer Glory, the pilot had to snare a spy's YT-1300 light freighter in order to disable it for capture by Imperial forces, and then assist in the capture of the yard itself. The pilot arrived in the system to find three Corellian transports aboard the station. With multiple transports, some fleeing from the arrival of Imperial forces, pilots had to move quickly to disable all transports and locate the spy. Rebel A-wings added to trainee frustration by acquiring missile locks as trainees scrambled to stop fleeing transports. After disabling all three transports, trainees had completed the primary objective, but could continue to aid in the capture of the platform, protect Imperial boarding craft, disable a Rebel B-wing, and destroy any other Rebel sympathizer craft in the area.[2]

Defender hangar IA

A TIE Defender leaves the hangar.

The third combat exercise demonstrated the ship's ability to operate independent of capital ships by inspecting vessels passing through a hyperspace jump point and disabling any vessels carrying contraband for capture by Imperial forces. After entering the system, pilots waited as cargo craft began passing through the sector, starting with Modular conveyors. Cargo ferries soon followed, one of which contained Rebels. Pilots could disable the craft for capture immediately upon the discovery, or wait until after inspecting the remaining transports, completing the primary objective. After disabling the contraband-carrying cargo ferry, trainees fended off multiple series of Rebel starfighters, protecting their command ship and boarding craft. All secondary and bonus objectives could be completed by eliminating all non-Imperial craft in the system, and successfully capturing the contraband.[2]

As a final test of the trainee's abilities, the pilot learned to use the TIE Defender as a light bomber to attack capital ships, using warheads to quickly eliminate their shields and ion cannons to disable them for capture. Armed with proton bombs, trainees arrived in system to discover two Rebel Ton-Falk-class escort carriers loaded with starfighters, but the primary objective only dictated the necessity of capturing one carrier. Despite the heavy payload, pilots used their wingmates to strategically assault at least one carrier by eliminating its weapon emplacements, being unable to completely lower the carrier's shields with projectile ordnance. Once the carrier was disabled, trainees had completed their primary objective and were able to continue with secondary and bonus goals of destroying an enemy frigate, corvettes, and various Rebel starfighters.[2]


Early development[]

The Empire's loss at the Battle of Yavin forced it to reconsider its tactics in fighting the Rebellion. Several new weapons projects were initiated as a result, among them the TIE Defender.[17] Such was the importance of the TIE Defender that the top secret development project was conducted under the supervision of top naval commanders,[6] including Grand Admiral Demetrius Zaarin,[2] then head of research and development for starfighter technology,[11] and the project would see several prototype stages before its completion shortly before the Battle of Endor[2] in 4 ABY.[29]

The initial prototype for the TIE Defender was the TIE/Ad x7, developed at the Sienar Advanced Research Division on Corulag[30] with input from Zaarin.[31] Although the tri-wing design of the ship was in place for the initial prototype, the ship was intended only as a test bed for the drive and targeting systems;[30] it did not have the final ion engines[32] and lacked the hyperdrive, ion cannons, and missile launchers which were incorporated into later prototypes and the final design.[30]

In early 3 ABY, the Empire launched a massive assault on the Rebel base on Hoth.[29][33] As the main Rebel forces struggled to delay the Imperials,[32] the Alliance's Renegade Squadron destroyed the weaponry on two Victory II-class frigates[34] as they attempted to escape. The Imperials decided to test out the TIE Advanced x7 prototypes and dispatched a unit of the vessels to join the fight.[32] However, the early models lacked the speed of the final version and, although they now included missile launchers, the ion cannons were still absent.[34] Six of the TIE Advanced x7 prototypes were destroyed by Renegade Squadron,[32] who also managed to board a Star Destroyer and steal one of the fighters to be studied by Alliance High Command.[34] The Empire dismissed the theft as unimportant, since the prototype lacked most of the systems planned for later models and, despite the prototypes' failure against the Rebels, the data collected during the battle proved useful to Sienar Fleet System's technicians in further developing the fighter.[32]

Final development and testing[]

"Those are only modified versions of the TIE advanced. We have something far more impressive to offer."
―Demetrius Zaarin, to Maarek Stele[1]

TIE Defender being advertised by Sienar Fleet Systems

Following the Battle of Hoth, Emperor Palpatine charged Grand Admiral Zaarin with the continuing development of the TIE series. Zaarin had all ongoing projects transferred to the XQ6 Platform Research in the Parmel system, including the TIE Defender and TIE Avenger, an evolution of Darth Vader's TIE Advanced x1 which Zaarin saw as merely a step towards completion of the TIE Defender. Both projects relied heavily upon the development of a hyperdrive which could be mass produced and would be small enough to fit inside the fuselage of a TIE fighter. When that proved problematic to Zaarin's team, the Grand Admiral managed to acquire the technology from the Habeen through a combination of diplomacy and military action against their rivals, the Nharwaak.[31] By the time that the TIE Avenger, modified by Zaarin to use the Habeen hyperdrive technology, entered service, the TIE Defender project had reached the final prototype stage[2] and the Empire was planning to roll the finished product out as a replacement for the Assault Gunboat.[35]

When the final prototypes were ready for inspection, Darth Vader instructed Zaarin to have six of the new fighters delivered to Emperor Palpatine on Coruscant for his personal review. Three cargo ferries from group Sela were sent to Zaarin's research facility to collect the prototypes, loaded into containers for transport. The Rebel Alliance attempted to disrupt the loading operation,n but their raiding party was defeated by Imperial fighters.[2]

The Empire soon learned that the Rebels were planning an ambush at Vinzen Neela 5, where the prototypes were to be transferred to the Imperial escort carrier Hininbirg. That time, Rebel fighters were joined by the CR90 corvettes Mar Duun and Vop Hui, which were attempting to plant a minefield around the rendezvous point. Responding quickly to the threat, Maarek Stele led a group of TIE Avengers to the rendezvous point, arriving before the Imperial ships to prevent the ambush and cover the transfer operation, allowing the Hininbirg to complete the delivery of the prototypes to Coruscant.[2]



A group of TIE Defenders fight Rebel forces.

After initial testing of the prototypes, the fighter entered service, deployed to a limited number of elite squadrons for full field testing.[15] The ship received an icy reception from those in the Imperial hierarchy. Many in the Imperial Navy who had not been privy to the starfighter's development were surprised by its sudden introduction. Some resented the ship due to a feeling that Zaarin had gathered too much power and prestige, while others saw the fact that the ship did not fit in with the traditional tactics of the Imperial Navy as an admission of failure,[32] leading to some resentment towards the ship, and the commanders that used them in battle.[9] Such was the level of resentment toward the ship that, had certain elements of the Imperial Navy known of its secret development, it is likely the project would have been abandoned before completion.[5] In the end, the field tests were never extensive and this, together with the Defender's prohibitive cost, meant that even an organization as wealthy as the Imperial Navy chose not to mass-deploy such a fighter.[15]

Some of the fighters were used to protect the TIE Experimental Project, another starfighter development project with which Zaarin was heavily involved. A handful of TIE Defenders from Shadow Squadron responded to the Rebel attack on the Bretie Facility, but were too late to prevent the loss of the facility. Members of Shadow Squadron were again involved in action against Rebel forces when the Alliance attacked the Obsidian research platform, but were destroyed along with the facility.[8]

Zaarin's betrayal[]

"We're no match for those TIE Defenders. Let's get out of here!"
―A TIE Avenger pilot — (audio) Listen (file info)[11]

The TIE Defender's most extensive use during the Galactic Civil War occurred when Zaarin attempted a coup against Emperor Palpatine. While Darth Vader led the search for the forces of the treacherous Admiral Harkov, Zaarin's forces attacked Vader's ship, the Star Destroyer Garrett. Although the Garrett survived, it had sustained damage that would prevent Vader from reaching Coruscant in time to warn the Emperor. However, the Garrett was one of the few ships to be carrying TIE Defenders, the Dark Lord of the Sith having brought them aboard in the hope of conducting operational trials. Vader selected five ace pilots, including Maarek Stele, to accompany him to Coruscant in the new starfighter.[2]

After escaping a trap set by Zaarin's Immobilizer 418 cruiser Harpago—destroying the ship with the help of the Nebulon-B2 frigate Osprey—they arrived at Coruscant to find the Emperor's Star Destroyer, the Majestic, badly damaged and the Emperor being taken to Zaarin's flagship, the Star Destroyer Glory. The TIE Defenders disabled the Emperor's shuttle and protected it while the Emperor was rescued by loyal forces.[2]

The Empire soon came to suspect that Zaarin had been planning his coup during the development of the TIE Defender, using its advanced technology to give him an advantage over loyalist forces. Indeed, Zaarin quickly attempted to ensure a technological advantage by eliminating TIE Avenger production facilities throughout the Empire. Although the Empire was unable to prevent the destruction of the facilities, Zaarin's own starfighters were used against him as TIE Defenders held his forces off long enough for Imperial personnel to evacuate and to prevent Zaarin from looting technology which could be used to produce his own TIE Avengers and TIE Defenders. They also proved instrumental in capturing magnetic pulse warhead technology from the Rebel station RS-32.[11]

Technological advantage[]

"It seems clear that Zaarin believed the technology embodied in the TIE Defender would give him the edge he needed to take out the Emperor. He did not foresee the extraordinary way in which you would turn his deadly weapon against him."
―Imperial briefing officer, to Maarek Stele — (audio) Listen (file info)[11]

TIE Defenders in battle

With the Empire's ability to manufacture TIE Avengers severely reduced, Zaarin continued to pursue a technological advantage over the Empire by targeting the research facility where he had overseen development of the TIE Defender. As Zaarin's forces attempted to escape with several TIE Defender prototypes, an Imperial strike force, consisting of TIE Defenders and assault transports, arrived to prevent the loss of the prototypes and recapture the base itself. The Empire succeeded in preventing Zaarin from acquiring most of the remaining TIE Defender prototypes and, after the facility was secured, the Star Destroyer Adarga arrived to defend it.[11]

Zaarin soon sent his own TIE Defenders and assault transports to retake the base. With the Adarga's supply of fighters insufficient to repel the attack and the research facility's shields not yet at full strength, the Empire was forced to call for reinforcements and deploy one of their few remaining TIE Defenders. Since Defenders were considered too valuable to destroy, Maarek Stele, piloting the Empire's TIE Defender, was given instructions to disable Zaarin's own TIE Defenders. Although the Empire succeeded in eliminating Zaarin's forces, even managing to capture some of his valuable TIE Defenders in the process, the Adarga took heavy damage and was forced to withdraw, leaving the base undefended.[11]

Zaarin had no intention of letting the Empire control the TIE Defender technology and led an assault to destroy the facility from the Glory. With the Adarga gone, the Empire was forced to evacuate the two remaining prototypes on the BFF-1 bulk freighter Mharsup, while the chief engineer fled with his team and the project data on the Lambda-class T-4a shuttle G'nabgib. A third TIE Defender, flown by Stele, assisted Delta-class JV-7 escort shuttles against Zaarin's fighters.[11]

In enemy hands[]

"Not a chance of getting a break from Zaarin's incessant TIE Defenders!"
―Imperial briefing officer — (audio) Listen (file info)[36]

From early in the ship's operational history, the TIE Defender attracted the attention of several other groups who attempted to acquire its technology. As Zaarin launched his coup, Hamo Blastwell, a Rebel agent posing as an Imperial officer, attempted to steal the plans to the starfighter from the Glory. Blastwell managed to escape, though Zaarin's crew prevented him from taking the plans.[1] The Rebels again came close to acquiring the technology as the Mharsup rendezvoused with the Assassin-class corvette group Hashim, near navigation buoy B-0F9, to transfer the prototypes to the safer ships for delivery to Admiral Thrawn, who was under orders to deliver them to a safe location. Shortly after the Imperials arrived at the rendezvous point, they came under attack from a Rebel strike team which attempted to capture the convoy. However, Imperial forces were able to hold off the Rebels until the transfer was complete and Hashim group fled to hyperspace.[11]


A cargo ferry delivers a new TIE Defender to Admiral Thrawn's Star Destroyer.

The Imperials' escape was short-lived as they came out of hyperspace into an ion cannon minefield set by Rneekii pirates. All three corvettes, as well as the G'nabgib, were quickly disabled. With the arrival of Assault Gunboat reinforcements, the Imperials were able to prevent the capture of the corvettes by pirate transports. The corvettes were still disabled and vulnerable, and the G'nabgib had been captured, giving the pirates access to the TIE Defender scientists. Although the Imperials suspected it would take some time for the pirates to replicate the technology, they knew that a program to create a counter to the fighter would need to be implemented immediately. The Empire quickly dispatched three cargo ferries from Mssan group to rescue the prototypes from the stranded corvettes. The transfer came under attack from Rebel starfighters and Zaarin's own TIE Defenders. While the Imperial forces battled the Rebels and Zaarin's forces, Nami pirates came out of hyperspace and used the distraction to capture the disabled Hashim 1 and escape with its TIE Defender. Though the Empire was able to finally take the remaining TIE Defenders to Thrawn. who saw them safely to Coruscant, the news that the technology had fallen into pirate hands presented a major threat.[11]

With the Empire's remaining TIE Defenders finally secured, they began a campaign to prevent the spread of the technology. The Rneekii pirates offered to ransom the lead scientist to the highest bidder. Although Zaarin negotiated with them, it was the Empire who made the highest bid and sent a shuttle to rendezvous with the pirates and conduct the exchange. Once the scientist was safely aboard, the Interdictor Red Claw arrived to trap the pirates while Imperial forces disabled and captured the transport carrying the ransom. The Nami pirates struck during the operation in an attempt to capture the scientist themselves—their leader, Ali Tarrak, was hoping to use the captured prototype as a model for producing their own TIE Defenders and sought the scientist's expertise. Although the Imperial forces succeeded in stopping the Nami from capturing the scientist, the Nami were able to inflict damage on the Red Claw's hyperdrive, leaving it stranded in the system. The Assassin-class corvette group Chemeti was sent to deliver supplies to the Red Claw and retrieve the rescued scientist. Zaarin sent his forces, including several TIE Defenders, to distract the Imperial forces, while his own corvette, using Chemeti 1's transponder code, collected the scientist.[11]

Missile Boat diplomacy[]

"Admiral Thrawn and the Emperor himself are gravely concerned over the possible proliferation of TIE Defenders. So potent a starfighter must not fall into enemy hands."
―Imperial briefing officer — (audio) Listen (file info)[11]

A TIE Defender under attack from a Missile Boat

Of even greater concern than the loss of the lead scientist was the news of a Nami attack on an Imperial cargo transfer area in the Yrrna system using TIE Defenders. Not only did this indicate that the Nami had begun production of their own TIE Defenders, but the presence of the Rebel Carrack-class cruiser Jester to observe the attack indicated that the Nami may be negotiating to sell the technology to the Rebel Alliance. Both the Emperor and Admiral Thrawn were concerned about the possible spread of the technology and the Empire resolved to eliminate all TIE Defenders in enemy hands. To that end, Admiral Thrawn had been secretly working with Cygnus Spaceworks to develop the Missile Boat—a starfighter specifically designed to counter the TIE Defender.[11]

The Missile Boat soon made its debut—Imperial spies learned that the Nami arms merchant cruiser Nuance was carrying TIE Defenders for sale to the Rebel cruiser Prism, and Thrawn ordered the capture of the fighters. Missile Boats engaged enemy forces while Thrawn, aboard the Star Destroyer Grey Wolf, oversaw the capture of the Nuance. The raid recovered eight TIE Defenders, which the Empire was able to retain, despite a subsequent Rebel attack on the Grey Wolf. The Empire also acquired many prisoners who, under interrogation, revealed the location of the manufacturing plant where Tarrak was producing the fighters. With Tarrak's Deep Space Manufacturing Facility located, Thrawn led the Grey Wolf's forces in a major attack on the facility, aimed at eliminating any further threat from the proliferation of TIE Defender technology. With her TIE Defenders caught unprepared, Tarrak's starfighters were quickly eliminated and her factory soon fell to a combined Missile Boat and TIE/sa bomber attack, while Tarrak herself was captured as her ship attempted to flee.[11]

Although the Empire had prevented TIE Defender technology from spreading further, Zaarin still possessed a number of the starfighters and continued to use them in his campaign against Thrawn's forces. The Missile Boat proved an effective foil to Zaarin's TIE Defenders and enabled the Empire to greatly diminish his supply of the fighters. By the time that Thrawn finally trapped Zaarin in the Unknown Regions, only a handful of the starfighters remained in the rogue Imperial's control.[36]

Other Imperial use[]

Defender IA

A TIE Defender approaches the Executor.

Some TIE Defenders were stationed aboard Darth Vader's flagship, the Executor. During the Battle of Mygeeto—as the Executor led Imperial forces in the invasion of the Rebel base on Mygeeto—the Imperial fleet came under attack from several Rebel capital ships, and Admiral Firmus Piett ordered use of TIE Defenders in the defense of the fleet. Flown by elite pilots, TIE Defenders aided in the destruction of the Rebel ships and the Empire went on to capture the Rebel base.[37]

A mixed squadron of TIE Defenders from the 29th Fast Attack Squadron and TIE interceptors from the 92nd Interceptor Squadron were stationed aboard the Nebulon-B frigate Mephitis while it was on assignment near Polis Massa. The TIE Defenders were tasked with defending the frigate as it conducted tests of the TIE/ph phantom, an Imperial starfighter fitted with an experimental cloaking device.[38] At some point, TIE Defenders participated in a Base Delta Zero orbital bombardment operation led by the Assertor-class Star Dreadnought Wrath. Similarly, TIE Defenders also operated around the Naval Station Validusia.[39] At one point, the Zann Consortium had the opportunity to acquire the ability to construct TIE Defenders by attacking Imperial assets in orbit of Corulag.[26]

In 4 ABY, the Empire lured the Rebel Alliance into attacking the second Death Star battlestation in orbit of Endor, where the Imperial Navy would be waiting to spring a trap.[29][40] At least one element of TIE Defenders, as part of Onyx Squadron, saw action at the Battle of Endor, but they were a very small minority of craft at the battle.[5] The lack of TIE Defender involvement in the ambush was of only minor concern within the Empire due to the significant number of TIE interceptors taking part.[41] The battle ultimately turned against the Empire and the small number of TIE Defenders were unable to make a significant impact.[5]

As the Empire began to crumble following the Battle of Endor and the death of Emperor Palpatine, the cost of the TIE Defender became an even greater factor and the model was decommissioned.[15] Although information obtained by the New Republic on Spirana in the year following the Battle of Endor indicated that there were over ten thousand production TIE Defenders unaccounted for,[25] the cessation of production prevented it from ever achieving widespread use.[15] Nonetheless, any TIE/D Defenders that were already created prior to being decommissioned were placed into groups such as Elite Force, at least two of which would later be used during the New Republic's Liberation of Coruscant to defend the Imperial Palace.[42]


"These are still out there. Not many, but even one is more than I'd like to face if I don't have to."
―Wedge Antilles[43]

TIE Defenders and Missile Boats in battle

The TIE Defender received some support from Countess Iran Ryad, an Imperial politician who trained as a starfighter pilot in her spare time. After the Battle of Endor, Ryad requisitioned a TIE Defender and quit her political role to take command of a group of four TIE Defenders charged with patrolling the coreward borders of the Empire. Ryad had her TIE Defender, the Red Star 1, heavily modified to enhance its shields, provide increased maneuverability through an upgraded engine, and allow increased firepower by tuning the fire control system. However, the modifications came at a high cost of 62,500 credits. After several successful patrols, Ryad took command of Red Star Squadron and began attacking any ships entering Imperial space without permission. Her actions brought her into conflict with her commanders and, after being charged with treason, she was eventually defeated by Baron Soontir Fel.[9]

Following Palpatine's death, the former Director of Imperial Intelligence and Prophet of the Dark Side Shadowspawn acquired many of the remaining TIE Defenders. Establishing a base on Mindor in the Taspan system, Shadowspawn used the vessels to launch a series of raids[25] in the Inner Rim, Expansion Region, and Mid Rim[39] aimed at capturing prisoners to serve as his Pawns. Over the course of two months[25] during 5 ABY,[25][44] the TIE Defenders were involved in dozens of raids on shipping. Despite the New Republic's efforts to capture a TIE Defender pilot in the hopes of learning Shadowspawn's location, a deadman interlock fitted to the fighters ensured that they were destroyed if the pilot was killed or lost consciousness. Rogue Leader Wedge Antilles eventually devised a plan to locate the base by attaching tracking devices to the hulls of TIE Defenders. The New Republic developed flechette torpedoes specifically to engage TIE Defenders—taking advantage of the TIE Defender's lack of particle shields, the torpedoes detonated into a cloud of durasteel shrapnel which would pierce the hulls of fighters that passed through. Within the cloud were hidden thousands of miniature tracking devices which would attach to the hulls of surviving fighters.[25]

Putting Antilles's plan into action, Rogue Squadron hid within a facsimile of the luxury liner Corellian Queen, while New Republic Intelligence leaked information that lured a TIE Defender squadron commanded by Captain Klick into an attack. The flechette torpedoes proved effective, allowing Rogue Squadron to destroy almost thirty percent of the enemy fighters, before the surviving TIE Defenders retreated, carrying the tracking devices with them. Though the devices were soon discovered, Shadowspawn, hoping to lure Jedi Knight Luke Skywalker to Mindor, allowed the New Republic to receive a signal from the devices, leading them to his base. TIE Defenders were heavily involved in the subsequent Battle of Mindor, engaging New Republic starfighters as they arrived in orbit of Mindor, and subsequently ambushing New Republic reinforcements, including the Millennium Falcon, as they approached the system.[25]

At some point following the Battle of Endor, the Force-sensitive Imperial clone X1 came into possession of several TIE Defenders, which were stationed aboard a Star Destroyer under his command when he traveled to Mustafar in order to create a clone army. X1's twin clone, X2, leader of the Rebellion's Grey Squadron, followed his brother to Mustafar in an effort to stop him. Landing aboard X1's orbiting Star Destroyer, Grey Squadron sabotaged the ship before escaping in X-wings. After defeating X1 in his personal TIE, the group were pursued by X1's TIE Defenders, but were able to destroy them before heading to the planet's surface.[12]

The TIE Defender resurfaced during the return of Grand Admiral Thrawn, though they were still deemed too difficult to produce and maintain, and remained both a minority within the Imperial fleet[7] and politically unpopular.[9] The few squadrons that remained in service were largely used to patrol the boundaries of what would become the Imperial Remnant.[9]

Isard's revenge[]

"Nice machines. I still prefer my X-wing, but I'll take a trip in a pinch."
―Wedge Antilles[21]
TIE Defender SotG

A flight of TIE Defenders

During the New Republic's campaign against Prince-Admiral Delak Krennel's Ciutric Hegemony, Rogue Squadron was sent in search of an Imperial superweapon near Distna. The superweapon rumors were bait to lure them into a trap, and they were quickly ambushed by six squadrons of TIE series starfighters. The Rogues were rescued from the trap by the arrival of two squadrons of TIE Defenders, Interloper and Stranger Squadrons, under the command of Colonel Broak Vessery. The Defenders hit Krennel's forces hard, using a combination of lasers and torpedoes to eliminate his remaining forces within five minutes of their arrival. Despite the Rogues' reluctance to trust the Imperials, they agreed to follow them back to their base before Krennel sent reinforcements.[21]

The Imperials were stationed at one of several secret Imperial bases throughout the galaxy. The base was one of the few facilities capable of producing TIE Defenders. It was an indication of the rarity of the TIE Defender that the three full squadrons of the fighters located at the base were more than Rogue Squadron's commander, General Wedge Antilles, thought had ever been built. The base was formerly under the command of General Arnothian, who had intended to use the TIE Defenders to establish himself as a warlord before Director of Imperial Intelligence Ysanne Isard disposed of him and took control of the facility.[21]

Isard claimed that she wanted peace with the New Republic. To that end, she had dispatched Vessery to aid the Rogues and then proposed to prove her intentions by helping them eliminate Krennel and rescue prisoners from her Lusankya, including famed Rebel Jan Dodonna. Isard would provide Rogue Squadron with TIE Defenders and cover identities to aid them in infiltrating Krennel's capital on Ciutric IV, posing as Imperial defectors. They would then eliminate the shield generators and defensive positions, allowing her forces to storm the prison. Meanwhile, a New Republic fleet would engage Krennel's forces.[21]

The Rogues quickly began training on the TIE Defender. Over the coming weeks, they engaged in frequent simulated battles against Interloper and Stranger Squadrons before departing for Ciutric. Although Isard betrayed both sides, using the Defenders, Rogue Squadron pilots successfully brought down the planetary shield of Krennel's capital, rescued the prisoners, and eliminated a clone of Isard herself. After the real Isard was killed in an attempt to retake the Lusankya, Vessery disappeared along with his two squadrons of TIE Defenders.[21]

Defenders remained in limited use under the Imperial Remnant, deployed in small numbers to the best pilots, rather than to entire squadrons. Shortly after the end of the Adumari Civil War, the Empire launched an assault on New Republic forces in orbit of Adumar. Among the Imperial fighters were four TIE Defenders in service of the 181st Imperial Fighter Wing under Turr Phennir, deployed in two pairs. These fighters acquitted themselves well and destroyed or disabled many New Republic starfighters. The Imperial forces were ultimately defeated and at least one of the TIE Defenders was destroyed in combat with members of Rogue Squadron, with Phennir's damaged and forced to withdraw.[45]

Yuuzhan Vong War and later use[]


A TIE Defender

Despite the Empire's long-held resistance to the TIE Defender, they would continue to be used by the Imperial Remnant until at least the end of the Yuuzhan Vong War, with the starfighters stationed on many Imperial capital ships, including Grand Admiral Gilad Pellaeon's flagship, the Right to Rule.[13]

During Operation Trinity, Captain Mynar Devis of the Immobilizer 418 cruiser Wrack personally flew one of three TIE Defenders escorting the Millennium Falcon to meet with Wedge Antilles's Alpha Fleet at Bilbringi, after the Yuuzhan Vong crippled several HoloNet relay stations, cutting off communication between Galactic Alliance forces. The group emerged from hyperspace to find Alpha Fleet embattled with Yuuzhan Vong forces and prevented from escaping by a Vua'spar interdictor. Devis sent one of his wingmates to inform Grand Admiral Pellaeon of the Yuuzhan Vong trap, while the others assisted the Galactic Alliance forces attacking the Vua'spar. Although they eliminated several enemy ships, both TIE Defenders were destroyed helping destroy the Vua'spar to allow Alpha Fleet to escape.[46]

As the war entered its final stages, the Yuuzhan Vong mounted a major attack on the Galactic Alliance capital of Mon Calamari. At the Battle of Mon Calamari, many TIE Defenders were deployed into combat as part of an elite strike team, with other notable squadrons such as Rogue, Twin Suns, and Vanguard Squadrons. Almost an entire squadron of TIE Defenders was incinerated when capital ships at the heart of the Yuuzhan Vong fleet fired Yaret-Kor plasma cannons en masse at the attacking starfighters.[13]

In 44 ABY,[44] former Imperial admiral and Galactic Alliance Chief of State Natasi Daala plotted to overthrow the Imperial Head of State, Jagged Fel. Daala gathered her forces—comprising her Maw Irregular Fleet and the fleets of Moffs Drikl Lecersen, Porrak Vansyn, and Trevin—over Exodo II in the Meridian sector, but news of the rendezvous had reached Fel, who was waiting to spring a trap. As the loyalist Imperial fleet engaged Daala's forces, Lecersen launched baradium missiles at key points on Fel's flagship, the Star Destroyer Gilad Pellaeon, forcing its crew to evacuate. Fel, along with his aide Ashik and his Jedi bodyguard Tahiri Veila, fled in three of the ship's complement of TIE Defenders. Despite their age, the starfighters' combination of speed and maneuverability enabled the three to reach the safety of the Turbulent-class Star Destroyer Bloodfin.[47]

Behind the scenes[]

Notable appearances[]


What might be a TIE Defender in Rebellion 5

The TIE Defender was created for Star Wars: TIE Fighter, a 1994 LucasArts video game, in which the craft was flyable by the player.[2] Although this craft was initially left out of the 1997 multiplayer game Star Wars: X-Wing vs. TIE Fighter for the sake of balance, the game data files still have an entry for the TIE Defender in the craft library, with the description field reading "Advanced space superiority fighter. This craft is too powerful to be put in this simulation. Dream on, fanboy!"[48] The TIE Defender returned in 1999's Star Wars: X-Wing Alliance, making an appearance in the single-player campaign and available as a player craft in the multiplayer mode.[8]

TIE Defenders appear in Star Wars Battlefront: Renegade Squadron and fighters which appear to be TIE Defenders can be seen in the comic book Rebellion 5, both of which take place before the canonical debut of the class after the Battle of Hoth, as established by TIE Fighter and repeated in numerous sources.[2][34][49] The appearance of the TIE Defender in Renegade Squadron was explained in the magazine The Official Starships & Vehicles Collection 67, which established them as early TIE Advanced x7 prototypes.[32]

The TIE Defender also appears in Star Wars: Empire at War: Forces of Corruption, in which the player, controlling the Zann Consortium, can acquire the technology. However, no canonical source has yet confirmed whether Tyber Zann took this opportunity.[26] The fighters also appear in the 2011 novel Fate of the Jedi: Ascension by Christie Golden, in which they are twice referred to as the "TIE Destroyer."[47] LEGO released a TIE Defender set in 2010. The LEGO TIE Defender has six missile launchers and a cockpit that rotates when the model turns.[50]

The 2012 reference book The Essential Guide to Warfare includes illustrations of TIE Defenders at the Naval Station Validusia and accompanying the Star Dreadnought Wrath during an orbital bombardment.[39] When asked about the presence of TIE Defenders in these images, illustrator Ansel Hsiao speculated that the units they were assigned to were considered of high importance due to the number of Star Dreadnoughts.[51]

Technical specifications[]


A TIE Defender

Many of the starfighter's specifications changed between TIE Fighter and X-Wing Alliance. The earlier game gave a speed rating of 155 MGLT, a maneuverability rating of 175 DPF, and a hull rating of 20 RU.[2] These were revised to 144 MGLT, 110 DPF, and 14 RU in X-Wing Alliance.[8] The shield rating was given as 200 SBD in TIE Fighter,[2] but was listed as 100 SBD in both TIE Fighter: The Official Strategy Guide[1] and X-Wing Alliance. Since it is the latest source, this article uses the values from X-Wing Alliance.[8]

There is also some discrepancy among sources as to the length of the TIE Defender. The Defender's Databank entry and The Official Starships & Vehicles Collection 67 describe it as 9.2 meters long;[6][20] however, TIE Fighter had originally given the length as 10 meters,[2] a length which was repeated in The Official Star Wars Fact File 73 and The Official Star Wars Fact File Part 53.[15][14] Furthermore, both The New Essential Guide to Vehicles and Vessels and More Starships! list the length as 6.6 meters.[7][9] The 9.2 meter length also appears in Coruscant and the Core Worlds as the length of the TIE Advanced x7, which served as the prototype for the TIE Defender.[30]

In both TIE Fighter and X-Wing Alliance, the TIE Defender is depicted as faster than both the RZ-1 A-wing interceptor and the TIE Interceptor.[2][8] This was reinforced by Star Wars: X-Wing Alliance: Prima's Official Strategy Guide, which described the ship as the "fastest and most maneuverable craft in the galaxy."[52] The figures given in The New Essential Guide to Vehicles and Vessels show it as faster than both, but only in an atmosphere, while its acceleration value is slightly lower than the TIE Interceptor and significantly below that of the A-wing.[7] The 2007 edition of Starships of the Galaxy describes the TIE Defender as "much faster than any other TIE variant," although it is unclear if this is referring to atmospheric speed or acceleration.[5] Star Wars: Rebellion: Prima's Official Strategy Guide states that "only the A-wing and TIE interceptor are more agile in battle."[27] This contradicts other sources, including the Databank and The Essential Guide to Vehicles and Vessels, which state that the TIE Defender was more agile than the TIE interceptor.[4][6]

Other inconsistencies[]

Both The Essential Guide to Vehicles and Vessels and the TIE Defender's Databank entry place the ship's cost at 300,000 credits.[4][6] However, More Starships! states that each unit cost 200,000 credits.[9] Starships of the Galaxy repeats the 200,000 credit value while simultaneously calling it "more than five times as expensive to produce as a standard TIE fighter." Since the cost of a TIE fighter is listed in the same book as 60,000 credits, the TIE Defender would have to have a 300,000 credit value to be five times the cost.[5] More Starships! established that the TIE Defender could carry consumables for two days.[9] Fantasy Flight Games' 2014 reference book Star Wars: Age of Rebellion Core Rulebook later revised this to one week. This article takes the later figure. Age of Rebellion Core Rulebook also describes the fighter's ion cannons as "cockpit-mounted,"[10] contradicting earlier sources, including The Essential Guide to Vehicles and Vessels, The New Essential Guide to Vehicles and Vessels and The Official Star Wars Fact File 73, all of which place them on the upper wings.[4][7][15]

The Official Star Wars Fact File 11 states that "the new TIE defender would not be at [the Battle of] Endor,"[41] which contradicts the Death Star II Limited expansion set for the Star Wars Customizable Card Game, The New Essential Guide to Vehicles and Vessels and Starships of the Galaxy, all of which establish that the pilots of Onyx Squadron used TIE Defenders during the battle.[5][7][23]



Notes and references[]

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 1.11 1.12 1.13 1.14 1.15 1.16 1.17 1.18 1.19 1.20 1.21 1.22 1.23 TIE Fighter Collector's CD-ROM: The Official Strategy Guide
  2. 2.00 2.01 2.02 2.03 2.04 2.05 2.06 2.07 2.08 2.09 2.10 2.11 2.12 2.13 2.14 2.15 2.16 2.17 2.18 2.19 2.20 2.21 2.22 2.23 2.24 2.25 2.26 2.27 2.28 2.29 2.30 2.31 2.32 2.33 2.34 2.35 2.36 Star Wars: TIE Fighter
  3. Star Wars: TIE Fighter identifies the ship as the "TIE Defender" while TIE is established as an acronym for "Twin Ion Engine" in several sources, including The Essential Guide to Vehicles and Vessels.
  4. 4.00 4.01 4.02 4.03 4.04 4.05 4.06 4.07 4.08 4.09 4.10 4.11 4.12 4.13 The Essential Guide to Vehicles and Vessels
  5. 5.0 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 Starships of the Galaxy, Saga Edition
  6. 6.00 6.01 6.02 6.03 6.04 6.05 6.06 6.07 6.08 6.09 6.10 Databank title TIE defender in the Databank (content now obsolete; backup link)
  7. 7.00 7.01 7.02 7.03 7.04 7.05 7.06 7.07 7.08 7.09 7.10 7.11 7.12 7.13 7.14 The New Essential Guide to Vehicles and Vessels
  8. 8.00 8.01 8.02 8.03 8.04 8.05 8.06 8.07 8.08 8.09 8.10 8.11 8.12 8.13 8.14 Star Wars: X-Wing Alliance
  9. 9.00 9.01 9.02 9.03 9.04 9.05 9.06 9.07 9.08 9.09 9.10 9.11 WizardsoftheCoast "More Starships!" (original article link) on Wizards.com (content now obsolete; backup link)
  10. 10.0 10.1 10.2 10.3 10.4 10.5 10.6 10.7 Star Wars: Age of Rebellion Core Rulebook
  11. 11.00 11.01 11.02 11.03 11.04 11.05 11.06 11.07 11.08 11.09 11.10 11.11 11.12 11.13 11.14 11.15 11.16 11.17 11.18 11.19 11.20 11.21 Star Wars: TIE Fighter: Defender of the Empire
  12. 12.0 12.1 Star Wars Battlefront: Elite Squadron
  13. 13.0 13.1 13.2 The New Jedi Order: The Unifying Force
  14. 14.0 14.1 14.2 The Official Star Wars Fact File Part 53 (TIE11-12, TIE/D Defender)
  15. 15.00 15.01 15.02 15.03 15.04 15.05 15.06 15.07 15.08 15.09 15.10 15.11 15.12 15.13 15.14 15.15 15.16 The Official Star Wars Fact File 73 (TIE11-12, TIE Defender)
  16. X-Wing: The Official Strategy Guide
  17. 17.0 17.1 17.2 17.3 17.4 17.5 17.6 Star Wars: The Official Starships & Vehicles Collection 67 (Legendary Craft: The TIE/D defender)
  18. SWAJsmall "Special Military Unit Intelligence Update" — Star Wars Adventure Journal 15
  19. Legacy of the Force: Betrayal
  20. 20.0 20.1 Star Wars: The Official Starships & Vehicles Collection 67 (In Command: The TIE/D defender)
  21. 21.00 21.01 21.02 21.03 21.04 21.05 21.06 21.07 21.08 21.09 21.10 21.11 X-Wing: Isard's Revenge
  22. Swccglogolg Star Wars Customizable Card GameSpecial Edition Limited (Card: TIE Defender Mark I) (backup link)
  23. 23.0 23.1 Swccglogolg Star Wars Customizable Card GameDeath Star II Limited (Card: Onyx 2) (backup link)
  24. Star Wars: The Official Starships & Vehicles Collection 67 (Starship & Vehicle Directory: The TIE/ad avenger)
  25. 25.0 25.1 25.2 25.3 25.4 25.5 25.6 25.7 Luke Skywalker and the Shadows of Mindor
  26. 26.0 26.1 26.2 Star Wars: Empire at War: Forces of Corruption
  27. 27.0 27.1 Star Wars: Rebellion: Prima's Official Strategy Guide
  28. Star Wars: Empire at War: Forces of Corruption Expansion: Prima Official Game Guide
  29. 29.0 29.1 29.2 The New Essential Chronology
  30. 30.0 30.1 30.2 30.3 Coruscant and the Core Worlds
  31. 31.0 31.1 Star Wars: The Official Starships & Vehicles Collection 67 (Welcome On Board: Grand Admiral Demetrius Zaarin)
  32. 32.0 32.1 32.2 32.3 32.4 32.5 32.6 Star Wars: The Official Starships & Vehicles Collection 67 (Action Stations: The defender attacks!)
  33. Star Wars: Episode V The Empire Strikes Back
  34. 34.0 34.1 34.2 34.3 Star Wars Battlefront: Renegade Squadron
  35. WizardsoftheCoast "Message to Spacers 7" (original article link) on Wizards.com (content now obsolete; backup link)
  36. 36.0 36.1 Star Wars: TIE Fighter: Collector's CD-ROM
  37. Star Wars: Imperial Ace
  38. FantasyFlightGamesLogo "Phantoms in the Dark" — Strongholds of Resistance
  39. 39.0 39.1 39.2 The Essential Guide to Warfare
  40. Star Wars: Episode VI Return of the Jedi
  41. 41.0 41.1 The Official Star Wars Fact File 11 (END8, The Battle of Endor)
  42. Star Wars: Galactic Battlegrounds: Clone Campaigns
  43. Star Wars: Imperial Handbook: A Commander's Guide
  44. 44.0 44.1 The Essential Reader's Companion
  45. X-Wing: Starfighters of Adumar
  46. The New Jedi Order: The Final Prophecy
  47. 47.0 47.1 Fate of the Jedi: Ascension
  48. Star Wars: X-Wing vs. TIE Fighter
  49. Rebellion 5
  50. 8087 - TIE Defender on LEGO.com Holobrick (archived from the original on May 13, 2012)
  51. 3D Star Wars projects thread by fractalsponge on www.scifi-meshes.com (April 9, 2012) (archived from the original on March 17, 2016)
  52. Star Wars: X-Wing Alliance: Prima's Official Strategy Guide

External links[]