TIE Advanced was the overall designation for a series of experimental TIE Fighter variants used by the Palpatine Empire.

TIE Advanced x1Edit

  • Name - TIE Advanced x1
  • Manufacturer - Sienar Fleet Systems
  • Line - TIE series
  • Model - Twin Ion Engine Advanced x1
  • Class - Starfighter
  • Length - 9.2 meters[1]
  • Max accel - 4,150 G
  • MGLT - 105 MGLT [1]
  • Max speed - 1,200 km/h [1]
  • Engine - 2 SFS P-s5.6 twin ion engines [2]
  • Hyperdrive - Class 4.0 [1]
  • Power - SFS I-s3a solar ionization reactor [2]
  • Shield - Equipped [3]
  • Hull - Reinforced durasteel alloy
  • Navigation - Equipped, 10 jump limit[2]}}
  • Armament - 2 L-s9.3 laser cannons [4], Cluster Missile launcher [3] with 20 cluster missiles
  • Crew - 1 Pilot [4]
  • Passengers - None
  • Capacity - 150 kilograms [1]
  • Consumables - 5 days [4]
  • Role - Space superiority fighter
  • Era - Rise of the Empire era [5], Rebellion era [6], New Republic era [7], New Jedi Order era[8]
  • Affiliation - Galactic Empire, Imperial Remnant

The TIE Advanced x1, or TIE/x1 was an advanced prototype starfighter touted as a replacement for the standard TIE Fighter and tested by Darth Vader at the Battle of Yavin and used by X1 during the Battle of Mustafar during the Galactic Civil War.

While it never made it into production, many of its best design features were later incorporated into the TIE/sa bomber and TIE/In interceptor. Further development of the Advanced continued, eventually leading to the TIE Avenger and TIE Defender.


TIEx1 egvv

TIE/x1 schematics

The TIE Advanced x1 featured a Sienar Fleet Systems I-s3a solar ionization reactor and paired P-s5.6 twin ion engines like the original TIE Fighter. However, the x1 had an original spaceframe, with an elongated rear deck and reinforced durasteel-alloy hull. The x1's most important innovation was the use of "bent-wing" solar array wings, like those used on the TIE/sa bomber, which had the advantages of increased surface area for more power while also reducing the craft's profile, compared to the TIE/ln starfighter's hexagonal panel wings.

Speed was only slightly improved due to the added mass of the vessel; a good deal of the extra power was bled off to the deflector shield generators. While less maneuverable than standard TIE fighters, it was more resilient in battle.

The 9.2 meter-long craft[1] had twin heavy L-s9.3 laser cannons in a fixed, front-mounted position, as well as a cluster missile launcher. In addition to its shields, it had a modest Class 4.0 hyperdrive but no life-support systems. The target tracking system was also more sophisticated than the already formidable advanced targeting system on standard TIE craft, used to overcome the extremely powerful electronic jamming used by all combat craft to defeat target lock in battle. For best performance, the targeting system of the x1 required frequent adjustment in combat.


Wishing to cut all ties with his Jedi past after his fateful duel, Darth Vader contacted Raith Sienar with a set of specifications for a new starfighter. Sienar and his team rose to the challenge and eventually presented Vader with the TIE Advanced x1 model. In 1 BBY, several months after the start of the Galactic Civil War, a renegade clone of the late Galen Marek stole Vader's TIE Advanced to escape Kamino and travel to Cato Neimoidia.[5] Vader continued to fly it often afterwards, and even went to some lengths to have it recovered and repaired when damaged at the Battle of Yavin 4.[9]

Armed with the references of a pleased Darth Vader, Sienar then presented his x1 to the Imperial Navy for mass distribution. The Empire, however, decided not to order the TIE Advanced x1 in large quantities, citing their excessive cost. Privately, some Imperial Navy strategists admitted that the Navy was afraid to purchase a fighter with a hyperdrive, fearing that it would give bureaucrats an excuse to slash orders for new capital starships. Some also feared that hyperdrive-equipped starfighters would facilitate defections. In the end, only a few squadrons were equipped with x1's. In addition, some x1s were assigned to various fleets that were considered of high importance to the Empire, such as fleets that had high mobility and thus needed hyperdrive-equipped starfighters.[10]As for the X1s, the reason I used those fighters is I imagined that strategic forces would have high mobility, thus requiring hyperdrive capable fighters. Such units would also have the priority necessary to access limited-production run craft. Limited production for a galaxy-spanning military could end up being quite a lot. A much more prosaic reason is that at the time the image was made, I didn't have any hyperdrive-capable fighter models completed except for the X1. (sic)
Ansel</ref> Nonetheless, Vader improved on the x1 design, eventually creating a modified version of the design that was also rumored to possess solar strakes to the panels.[11]

TIE Advanced Marvel

TIE Advanced x1's during an attack on the Wheel.

The few ships built were carried aboard Star Destroyers and other Imperial vessels. TIE Advanced x1s were deployed from Commander Strom's Pursuit-class light cruiser to stage an attack on the Wheel, which the Empire blamed on the Alliance to Restore the Republic, excusing the Imperial takeover of the station.[12] Storm Squadron was known to use x1s extensively.[13] Several x1 starfighters were also in a fleet gathering observed by Admiral Kendal Ozzel and Captain Firmus Piett at some point between the former's promotion to Admiral and the latter's promotion to Admiral.[14] The x1's presence among the fleet was largely due to their hyperdrives, due to the fleet's high mobility.[10]

The Empire instead opted for the TIE/In interceptor, which featured the TIE Advanced x1's drive system in a more compact ship. Although the TIE interceptor lacked a hyperdrive and shields, it was blindingly fast, incredibly maneuverable, and significantly cheaper than the TIE Advanced x1. By the Battle of Endor, the large increase in TIE Interceptor production meant the end of production for the TIE Advanced x1. The Advanced x1's bent-wing solar array wings were the same as the wings used on the similar but twin-hulled TIE/sa bomber.

The fighter flown by Vader at Yavin was repaired when he reached Imperial Relay Outpost V-798.[9] Vader had it with him on the Terror, while overseeing the TIE Phantom project. When the Terror was destroyed by Rebel operatives, Vader escaped in his fighter.[15] Vader again utilized his TIE Advanced x1 during the Battle of Hoth. However, his ship was damaged and rendered inoperative by Rebel starfighters.[16]


A TIE Advanced x1 and TIE Fighters engaging Alliance to Restore the Republic T-65 X-wing starfighters near the second Death Star

It was later stowed aboard the Executor and was apparently vaporized when the ship collided with the second Death Star during the Battle of Endor, though at least one TIE Advanced x1 was involved in the space battle over the sanctuary moon.[17] One of Vader's other TIE Advanced x1 models was discovered by Jaden Korr in a hangar at Darth Vader's former stronghold on Vjun.[18] Also, the Sith Lord X1 flew such a ship during the Battle of Mustafar.[7] During the First Battle of Coruscant, At least two TIE Advanced x1s, utilized by Elite Force, were tasked with guarding the Imperial Palace, although they ultimately failed.[19]

By the beginning of the Yuuzhan Vong War, enough of these ships had been made that some ended up in the hands of private parties such as Lando Calrissian, who used a modified TIE Advanced x1 for entertainment purposes in the asteroid belt at Dubrillion. During the First Battle of Dubrillion, Jacen, Jaina, and Anakin Solo flew three of these fighters against Yuuzhan Vong coralskippers.[8]

Behind the scenesEdit

In early blueprints for the Imperial I-class Star Destroyers, fighters known as "TIE Assault Craft" could be seen as part of the fighter complement. These bent-wing craft might have been TIE Advanced x1s with a different name or possibly a sister craft of the x1.

The size comparison chart found in the 2011 reference book Millennium Falcon Owner's Workshop Manual seems to suggest a different length for the x1. By using the well documented sizes of the Millennium Falcon and the T-65 X-wing starfighter as a scale, the resulting size is roughly 7.6 meters.

The x1 is armed with a supply of cluster missiles in its appearance in the game Star Wars: Rogue Squadron II: Rogue Leader.

The x1 appears to have navigation lights that are like fog lights.

In the 2011 science-fiction film Super 8, a model of a TIE Advanced x1 can be seen hanging in Joe's room.

Various x1 starfighters were seen in the background of an artwork by Tommy Lee Edwards depicting Admiral Ozzel and Captain Piett observing a fleet gathering in the 2012 guidebook The Essential Guide to Warfare. The background itself uses a picture from Ansel Hsiao's personal gallery as a background, originally titled "Strategic Reserve."[20] According to Ansel Hsiao in an email, when he was creating the artwork, he chose the x1 starfighters to be among the fleet for a few reasons: He hadn't completed any TIEs that utilized a hyperdrive outside of the x1 at the time the artwork was made, and he envisioned the fleet in question as being a high mobility fleet, which required fighters that possessed a functioning hyperdrive. He reasoned that with those needs, units such as the fleet in the image were important enough to have access to limited-production fighters, and that limited-production fighters in a galaxy-spanning empire would still mean a lot of fighters in a relative sense.[10]


  • Canon
    • Star Wars: Galactic Battlegrounds
    • Star Wars Battlefront: Elite Squadron
    • Boba Fett: Enemy of the Empire 1
    • Star Wars: The Force Unleashed II
    • Star Wars: Empire at War
    • Star Wars: Empire at War: Forces of Corruption
    • Star Wars: Empire 3: Betrayal, Part 3
    • Star Wars: Empire 5: Princess... Warrior, Part 1
    • Star Wars Journal: The Fight for Justice Template:Imo
    • Star Wars Episode IV: A New Hope First appearance
    • Star Wars: Trench Run
    • Star Wars Episode IV: A New Hope junior novel
    • Star Wars Droids 8: Star Wars According to the Droids, Book III
    • Star Wars: Empire 15: Darklighter, Part 4
    • Star Wars 6: Is This the Final Chapter?
    • Star Wars: Rogue Squadron II: Rogue Leader
    • Star Wars: Rogue Squadron III: Rebel Strike
    • Perfect Evil
    • Oh!! Jawajawa]
    • Star Wars: Empire 14: The Savage Heart
    • Star Wars Missions 17: Darth Vader's Return
    • Star Wars Missions 18: Rogue Squadron to the Rescue
    • Darth Vader Strikes
    • Star Wars 18: The Empire Strikes
    • Star Wars 20: Deathgame
    • Star Wars 21: Shadow of a Dark Lord
    • Star Wars 29: Dark Encounter
    • Star Wars 35: Dark Lord's Gambit
    • Star Wars 37: In Mortal Combat
    • Star Wars: Rebellion 1: My Brother, My Enemy, Part 1 Featured in a Flashback</ref>
  • Template:Tales
  • Classic Star Wars 2
    • Splinter of the Mind's Eye Mentioned only
    • Splinter of the Mind's Eye 4 Mentioned only
  • Star Wars Episode V: The Empire Strikes Back junior novel Template:Imo
    • Star Wars 52: To Take The Tarkin
    • Shadows of the Empire
    • Star Wars: Rebel Assault II: The Hidden Empire
    • Star Wars Battlefront: Renegade Squadron
    • The Rise and Fall of Darth Vader Mentioned only
    • A Day in the Life
    • X-wing Rogue Squadron: The Warrior Princess
    • Star Wars: Jedi Knight: Jedi Academy
    • Star Wars: Union
    • Vector Prime (novel)
    • Star Wars: Imperial Ace
    • Template:SWG
  • Non-canon appearances


    • LEGO Star Wars: The Complete Saga
    • LEGO Star Wars: The Quest for R2-D2
    • Prey Template:Am
  • LEGO Star Wars II: The Original Trilogy
    • Star Wars Infinities: A New Hope
    • Tag & Bink Are Dead
    • The Long, Bad Day
    • Collapsing New Empires Template:Am


    • Star Wars (toy line)|Star Wars toy line
    • Star Wars: The Power of the Force (1995)
    • Star Wars Sourcebook
    • The Stele Chronicles
    • TIE Fighter: The Official Strategy Guide
    • Star Wars: Incredible Cross-Sections
    • Template:SOTE Template:Imo Template:C
    • Star Wars Gamemaster Screen, Revised]]
    • The Essential Guide to Vehicles and Vessels
    • Template:CCG
    • Star Wars: Behind the Magic
    • Star Wars: The Action Figure Archive
    • Rogue Squadron II: Rogue Leader: The Official Nintendo Player's Guide
    • Template:FFCite
    • [Hero's Guide
    • The New Essential Guide to Vehicles and Vessels
    • Star Wars: The Official Starships & Vehicles Collection 8
    • Star Wars: Complete Cross-Sections
    • Vader: The Ultimate Guide
    • Template:GamerCite
    • Template:SWGTCG
    • Template:SWGTCG
    • Millennium Falcon Owner's Workshop Manual
    • Template:DB
    • Star Wars: Beware the Sith
    • Template:SonyCite
  • Notes and references
  1. 1.0 1.1 1.2 1.3 1.4 1.5 Star Wars: Behind the Magic
  2. 2.0 2.1 2.2 The Official Star Wars Fact File
  3. 3.0 3.1 Rogue Squadron II: Rogue Leader: The Official Nintendo Player's Guide
  4. 4.0 4.1 4.2 Star Wars: Complete Cross-Sections
  5. 5.0 5.1 Star Wars: The Force Unleashed II
  6. Star Wars Episode IV: A New Hope
  7. 7.0 7.1 Star Wars Battlefront: Elite Squadron
  8. 8.0 8.1 Vector Prime
  9. 9.0 9.1 Star Wars: Empire 14: The Savage Heart
  10. 10.0 10.1 10.2 Hsiao's explanation
  11. Star Wars Galaxies
  12. Star Wars 18: The Empire Strikes
  13. Star Wars PocketModel TCG
  14. The Essential Guide to Warfare
  15. Star Wars: Rebel Assault II: The Hidden Empire
  16. Star Wars Battlefront: Renegade Squadron
  17. ScreenThemes
  18. Star Wars: Jedi Knight: Jedi Academy
  19. Star Wars: Galactic Battlegrounds: Clone Campaigns
  20. Template:Cite web

TIE Advanced x2Edit

  • Name=TIE/x2 starfighter
  • Manufacturer=Sienar Fleet Systems
  • Designer[TIE Mod Team
  • Model=TIE/x2
  • Class=Starfighter
  • Engine=Ion engines
  • Firs tuse=0 ABY (35:4 GrS)
  • Era=Rebellion era
  • Affiliation=Galactic Empire

The TIE/x2 starfighter was a TIE series starfighter prototype created by Sienar Fleet Systems.


It incorporated many of the design innovations from the TIE Advanced x1, including higher performance ion engines than the TIE/ln starfighter, a hyperdrive, and improved combat software; it also possessed a hull that was a departure from the TIE series standard, and inward-swept solar/radiator panels configured for higher pilot visibility.


Thirty-two TIE/x2 starfighters went through field trials for nine months under some of the best active duty TIE wing commanders in the Imperial Navy, where they were carefully monitored by teams of diagnostic droids, maintenance techs, and engineers; their reports (along with glowing reports from the pilots themselves) gave the SFS TIE Mod Team a solid profile of the ships' perks and flaws. The ships were returned to Lianna at the close of the trials.

Behind the scenesEdit

This is likely the same ship type as, or a predecessor of, the TIE Advanced ships seen in the Star Wars: X-wing game, despite Imperial Defense Daily's report claiming that the ship was not to see active duty service. It is probably also the TIE Advanced model mentioned in The Far Orbit Project.

A string in Star Wars: Empire at War: Forces of Corruption has TEXT_UNIT_TIE_TANBRIS as the string's name, with TIE Advanced X-2 as the data in the string, however no unit uses this string, and there is no TEXT_TOOLTIP string to go with it as its description as there is for all other units. Probably the x2 was planned to be in the game, but was canceled early on, and its name string was left in.


  • Galaxywide NewsNets

TIE Advanced x3Edit

  • Name=TIE/x3 starfighter
  • Manufacturer=Sienar Fleet Systems
  • Designer=TIE Mod Team
  • Model=TIE/x3
  • Class=Starfighter
  • Engine=Ion engines
  • First use=2 ABY (37:5 GrS)
  • Era=Rebellion era
  • Affiliation=Galactic Empire

The TIE/x3 starfighter was a TIE testbed created by Sienar Fleet Systems.


It incorporated many of the design innovations from the TIE Advanced x1 and TIE Advanced x2 models, including higher performance ion engines than the standard TIE/ln starfighter, improved combat software, and inward-swept solar/radiator panels configured for higher pilot visibility.

However, its hullform was more consistent with the TIE fighter, rather than the experimental departures of the TIE/x1 and TIE/x2. It also lacked those models' hyperdrives. It is likely that this was the prototype for the [TIE Interceptor.


  • Galaxywide NewsNets Mentioned only

TIE/IN InterceptorEdit


  • Name=TIE/In interceptor
  • Manufacturer=Sienar Fleet Systems|[1]
  • Line=TIE series
  • Model=Twin Ion Engine Interceptor
  • Class=Starfighter
  • Length=9.6 meters[2]
  • Max accel=4,240 G or 21 MGLT/second[3]
  • Mglt=111[3] MGLT[2]
  • Max speed=1,250 km/h[2]
  • Engine=SFS P-s5.6 twin ion engines[1] (rated 175 KTU)
  • Hyperdrive system=None standard[1], can be equipped as upgrade[4]
  • Power=SFS I-s3a solar ionization reactor[1]
  • Shield gen=None standard; can be equipped as upgrade
  • Hull=Titanium alloy hull (16 RU)[3]
  • Sensor=SFS S-c4.1 multi-range TAG
  • Target sensor=SFS T-s9a targeting computer
  • Navigation sensor=SFS N-s6 Navcon
  • Avionics=SFS F-s4 flight avionics system
  • Armament
    • Original design: SFS L-s9.3 laser cannons (4)[2]
    • Later refit: SFS L-s9.3 laser cannons (2) and Blaster cannons (4)
    • Multipurpose Warhead Launchers can be mounted with optionally varying payload (2)
  • Crew=Pilot (1)[1]
  • Cargo capacity=75 kilograms[2]
  • Consumables=2 days[1]
  • Othersystems=*AE-35 subspace transceiver, Ejection seat
  • Role=*Space superiority fighter, [Interceptor
  • Era=Rebellion era[5], New Republic era, New Jedi Order era, Legacy era
  • Affiliation=Galactic Empire,[6], New Republic, Imperial Remnant, Galactic Federation of Free Alliances, Peace Brigade

{{Quote|Your generic TIE grunt is just plain suicidal. And the TIE Defender jockey is bloodthirsty. But the TIE Interceptor pilot, he's suicidal and bloodthirsty. When you see a squad of those maniacs flying your way, you'd better hope your hyperdrive is operational.Kyle Katarn - The New Essential Guide to Vehicles and Vessels

The TIE/in starfighter, or TIE Interceptor, was a TIE series starfighter used by the Galactic Empire. The TIE Interceptor was identifiable by its arrow-shaped solar collection panels, a distinct difference from the hexagonal solar arrays of its predecessor, the TIE Fighter. The Interceptor was one of the fastest starfighters in the galaxy at its prime, nearly rivaling the Alliance to Restore the Republic's RZ-1 A-wing interceptor.

Due to their speed, distinct shape, and narrow profile in comparison to the TIE/ln starfighter (which was nicknamed "eyeball"), TIE Interceptors came to be referred to occasionally as "squints" by enemy pilots.[7]


File:TIE Interceptor by Darren Tan.jpg

Like most TIE models, the TIE Interceptor shared nearly identical cockpits, drive pods, and wing brace designs with the TIE Fighter. The solar collector panels were lengthened and angled, and the forward center section was removed. This new solar array design gave the Interceptor its unmistakable dagger-like appearance, while providing the pilot with increased visibility and shrinking its profile to make targeting more frustrating for enemy gunners.[8] This wing design gave the craft a more menacing visage, continuing the Empire's reputation of ruling through fear.[9]

The original production model came equipped with four L-s9.3 laser cannons, one installed on each wingtip. New targeting software was, among other advancements, installed in the TIE Interceptor, and the SFS T-s9a targeting computer offered greater accuracy during complex flight maneuvers.[10] Twin laser cannon hardpoints still remained on the "chin" portion of the cockpit module. Provided that technicians could find room for additional power generators, these cannons could also be utilized.[8]

Later TIE Interceptor models were modified to carry four blaster cannons, replacing the original wingtip laser cannons, along with twin chin-mounted laser cannons. However, the older model remained a common sight in Imperial fleets for years to come.[11]


The TIE Interceptor fielded P-s5.6 twin ion engines.[10] The new engines included an advanced ion-stream projector, thus allowing pilots access to more sophisticated combat maneuvers. Twin-port deflectors supported this feat by allowing the pilot individual manipulation of the deflectors, thus providing finer flight control.[8] These advancements in engine technology made the TIE Interceptor a superior platform in space combat, achieving speeds beyond all other Alliance starfighters short of the RZ-1 A-wing interceptor.[12]

The TIE Interceptor's primary role was as its title suggested. Like its predecessors, the Interceptor lacked heavier armor, deflector shields, a hyperdrive, and life support systems.[8] Interceptor pilots were forced to rely on speed, maneuverability, superior numbers, and advanced weapon systems to prevail in its primary role of space superiority.[8] The craft's drawbacks meant that any pilot who survived more than a few missions was considered to be a "top gun" in the Imperial fleet.[13]

With no hyperdrive, the TIE Interceptor was reliant on a capital ship for an operations base. Star Destroyers and prominent shipyards such as Kuat and Fondor were common staging areas for Interceptor squadrons; however, smaller vessels and more remote locations had to rely on aging TIE fighters.[8]


There was also a special variant, painted completely red with significant upgrades, that was available for use by the Emperor's Royal Guards. Aside from its paint job and upgrades, this model also featured two small wings protruding from each solar panel.[14]

TIE Interceptors had powerful solar ionization reactors, the same model used in the TIE Avenger. These could handle the special equipment built into the Interceptor, including deflector shields, beam weapons such as special beam jammers, decoy beams, hyperdrives and extra missile racks for increased warhead payload. It was common for Alpha Squadron, Avenger Squadron, Delta Squadron, Gamma Squadron, Sunspot Squadron, and others to carry one or most of these pieces of special equipment at a time.[10][15][16]


The TIE Interceptor was designed to have the power of the TIE/Advanced starfighter but be more cost-effective, as the TIE/Advanced was too expensive to mass-produce.

TIE Interceptors were the new fighter force of the Empire after the Battle of Yavin, but it seems that test models were frequently seen in space battle prior to and during that time in campaigns such as Operation Strike Fear and Operation: Skyhook.[17]

Emperor Palpatine, aware of the superior abilities of the TIE Interceptor, as well as its relatively low cost, had planned to replace all standard TIE Fighters with Interceptors. By the Battle of Endor, TIE Interceptors filled twenty percent of the total Imperial starfighter complement, and overwhelmed many Rebel fighters.[8]

TIE interceptors dueled with the Rebel's premier T-65B X-wing starfighter squadron, the Rogues, in numerous battles[18] around six months after the destruction of the Imperial Death Star.[13] A TIE Interceptor captured at the Liberation of Gerrard V was stored in the Rogue's hangar.[18]

File:TIEinterceptor negvv.jpg

The TIE Interceptor was considered one of the best, if not the best starfighters for dogfighting. It was often used by elite Imperial TIE squadrons like the 181st,[19] the 128th,[13] Alpha Squadron, and Avenger Squadron. The Interceptor was also used by squadron leaders in TIE/Ln starfighter squadrons, as well as being used by Imperial personnel not in the Imperial TIE Fighter Corps, or the Imperial Navy.[8][20][3]

Modified TIE Interceptors were used by Warlord Zsinj in an attempt to bait and kill Wedge Antilles. Finding that Wraith Squadron and Rogue Squadron, under Antilles' leadership, were significant impediments to his plans, the Warlord modified twelve Interceptors with droid brains and high-explosives. These ships would fly under the coordination of a central computer and be paired with a piloted craft. They were intended to close with enemy craft and detonate their explosive payloads. The two squadrons thus formed pretended to be the Imperial 181st Fighter Squadron under the command of Baron Soontir Fel.[21]

The Warlord knew that Antilles and Fel had a personal relationship, though he was unaware of its true nature. Using actors such as Tetran Cowall and computer voice modification, he was successful in his efforts to deceive Antilles. However, Voort saBinring deduced that the ships must be automated and jammed their signal, making them easy prey for the Wraiths and Rogues combined. Finally, Wedge splashed Fel's ship, only to discover Tetran Cowall instead of the Baron.[21]

Due to limited pilots and fighters, Grand Admiral Thrawn had many TIE Interceptors fitted with shields to minimize casualties during his reign of the Imperial Remnant. This practice was continued after his death as the Empire could no longer afford to field profuse fleets of TIE Fighters.[22]

Officers of the Imperial Navy were sometimes known to adopt TIE Interceptors as their personal craft, installing shield projectors and hyperdrives so the Interceptors could be utilized as escape vehicles. Apwar Trigit was one such officer.[4]

The TIE/In starfighter later became the basis of the Predator-class fighter.[23]

Behind the scenesEdit

File:TIEint schem.jpg

Several sources state that the TIE/In was the main reason behind the development of the RZ-1 A-wing interceptor by the Rebel Alliance (as a countermeasure) and that the Interceptor was deployed after Yavin.

However, the existence of the TIE Interceptor around the Battle of Yavin was well established in the timeline. Interceptors made appearances in Star Wars: X-wing, Star Wars: Battlefront II, Star Wars Episode III: Revenge of the Sith video game, LEGO Star Wars II: The Original Trilogy, LEGO Star Wars: The Complete Saga (though the Lego Star Wars games are non-canon), and Star Wars: Lethal Alliance, all of which take place before, during, or shortly after the Battle of Yavin. West End Games' Star Wars Sourcebook stated that at the time of Yavin, standard Imperial Star Destroyers carried one squadron of Interceptors (12 craft), one Bomber squadron, and four TIE/Ln starfighter squadrons. By the time of the Battle of Endor, an additional Interceptor squadron has replaced that of the TIE/ln.

Numerous sources depict the TIE Interceptor as having only four wingtip cannons, but their very first appearance, in Return of the Jedi, shows them firing their chin-mounted fifth and sixth cannons, in addition to their wingtip cannons throughout the Battle of Endor. It has since been established that each TIE Interceptor comes equipped with cannon mountings on the chin, like the preceding TIE Fighter, allowing for the addition of two more cannons.

In 1998, players could fly the Interceptor in unlocked missions in the Star Wars: Rogue Squadron video game if they earned all silver medals during the campaign.

The post-production speed/maneuverability chart for Return of the Jedi lists the TIE Interceptor as being able to go up to 125 MGLTs and having a maneuverability rating of High.[24]

Many of the models of the TIE Interceptor used in Return of the Jedi have four laser cannons on their wingtips; however, the main model used in the "Return of the Jedi collection" section of the Blu-ray special edition only has two laser cannons total, on the top two wingtips. That may be due to the fragility of the model kit parts used to create the cannons, as publicity photos taken around the time of Return of the Jedi show the miniatures with four wingtip cannons.


Template loop detected: Template:Scroll box


Template loop detected: Template:Scroll box

Notes and referencesEdit

  1. 1.0 1.1 1.2 1.3 1.4 1.5 Star Wars: Complete Cross-Sections
  2. 2.0 2.1 2.2 2.3 2.4 Star Wars: Behind the Magic
  3. 3.0 3.1 3.2 3.3 Star Wars: X-wing vs. TIE Fighter
  4. 4.0 4.1 X-wing: Wraith Squadron
  5. Star Wars Episode VI: Return of the Jedi
  6. Battlefront II: Prima Official Game Guide
  7. Alliance Intelligence Report: TIE Fighters
  8. 8.0 8.1 8.2 8.3 8.4 8.5 8.6 8.7 The Essential Guide to Vehicles and Vessels
  9. Imperial Sourcebook
  10. 10.0 10.1 10.2 The Stele Chronicles
  11. The New Essential Guide to Vehicles and Vessels
  12. Rogue Squadron II: Rogue Leader: The Official Nintendo Player's Guide
  13. 13.0 13.1 13.2 Rogue Squadron: Official Nintendo Player's Guide
  14. Star Wars Galaxies
  15. TIE Fighter: The Official Strategy Guide
  16. Balance of Power in the Airam Sector
  17. Star Wars: X-wing
  18. 18.0 18.1 Star Wars: Rogue Squadron
  19. X-wing Rogue Squadron: In the Empire's Service
  20. Star Wars: TIE Fighter
  21. 21.0 21.1 X-wing: Solo Command
  22. Template:DB
  23. Star Wars: Legacy 0
  24. Return of the Jedi Sketchbook, page 95

External linksEdit

Royal Guard TIEEdit

Template:Ship The Emperor's Royal Guard TIE/In starfighter was a specially modified version of the TIE/In interceptor. These TIE Interceptors were flown only by Emperor Palpatine's Royal Guard.



A T-Wing under attack from a Royal Guard starfighter.

These starfighters were commonly used to escort Emperor Palpatine's Lambda-class shuttle and its decoys during his travels. Displaying the distinctive crimson red color of the Royal Guard, these deadly war machines struck fear into any opposing fighters. Royal Guard fighter wings were thought to even rival the skills of elite pilots from the 181st Imperial Fighter Wing and Rogue Squadron. These fighters were said to have been commissioned by Palpatine himself. 

Under the supervision of Darth Vader, Imperial workers spent many long hours modifying TIE Interceptor fighters. Unlike the original TIE Interceptor, the Royal Guard TIE Interceptor was equipped with a built-in hyperdrive and shield generator, while also having blazing speeds and fantastic maneuverability that exceeded that of its fleet counterpart. On very rare occasions, these fighters found places outside of the Royal Guard, and were thus subject to even further modification, including more devastating weapons, more advanced shielding technologies, and, in rare cases, ordnance launchers. By contrast, regular Interceptors with similar added equipment, such as shield projectors, warhead launchers, and hyperdrives (for instance that of Apwar Trigit) suffered reduced speed and maneuverability. Vader himself, however, never flew a Royal Guard TIE Interceptor, though he had on occasion piloted a TIE Advanced x1 and a TIE Defender.

It is unclear how the Royal Guard TIE Interceptor, described as having blazing speed and fantastic maneuverability while also having a hyperdrive and deflector shields, would compare against the TIE Avenger or TIE Defender, two other exceptional starfighters produced by Sienar Fleet Systems. One thing is for sure is that the Royal Guard craft underwent extensive modification from the original Interceptor, whereas the Avenger and Defender featured different platforms and newer technology than the Interceptor. During Palpatine's near capture by the traitor Admiral Zaarin, no Royal Guard Interceptors were present as the Emperor was rescued instead by Defenders flown by Vader and Maarek Stele.

Behind the scenesEdit


The Royal Guard TIE Interceptor was introduced in Rage of the Wookiees, the second expansion of Star Wars Galaxies. It is a quest reward for Imperial pilots for completing a series of quests from the Civilian Protection Guild.

In 2007 Hasbro released a die-cast model of the Royal Guard TIE Interceptor as part of their Titanium Series.



Notes and referencesEdit

External linksEdit

TIE Advanced x7Edit

Template:Ship The TIE Advanced x7, also known as the TIE/Ad Defender prototype, was a prototype for the TIE/D Defender developed at Sienar Fleet Systems' Advanced Research Division on Corulag.


Intended only to serve as a testbed for the Defender's drive system and primary weapon targeting system, The TIE/Ad x7 lacked the ion cannons and missile launchers that were implemented on the eventual TIE Defender design. Nevertheless, decades of experience and advances in TIE technology went in to the construction, resulting in a starfighter that was a radical departure from previous models in terms of appearance and performance.

The Advanced x7 featured three solar panels arranged around the spherical, central cockpit, which gave a large boost to the ship's power plant, allowing the ion engines to achieve speeds only previously possible in a light interceptor model. Additionally, triple arrays of maneuvering jets mounted on the solar collectors gave the starfighter a high level of agility in flight and combat.


The TIE/Ad x7 was one of the last TIE prototypes developed prior to the fall of the Galactic Empire.


TIE/D DefenderEdit

Template:Eras Template:Youmay Template:Ship {{Quote|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 - |The New Essential Guide to Vehicles and Vessels The TIE/D Defender, commonly known as the TIE Defender, was a high-performance TIE series starfighter developed for the Imperial Navy by Sienar Fleet Systems 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 firepower, made it arguably the most advanced starfighter available at the time.

The ship'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 starfighter played a major role in the Empire's campaign against rogue Grand Admiral Demetrius Zaarin and units participated in several other battles including the Battle of Endor. However, the advanced starfighter attracted the attention of several other factions and the Empire struggled to prevent the spread of the technology.

Following the death of Emperor Palpatine at Endor, the TIE Defender continued to see limited use by the Imperial Remnant up to at least 44 ABY, and was involved in numerous conflicts, including the Yuuzhan Vong War.


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. That led to the introduction of the TIE Advanced x1[1] and its successor, the TIE Avenger,[2] and the TIE Defender itself was touted as the next "logical advance" of the TIE series—a starfighter that was fast, well armed and capable of hyperspace travel.[3]

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

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.[1] Like previous TIE models, the TIE Defender lacked life support systems and pilots were required to wear the standard sealed TIE pilot flight suit. However, in a departure from the design of previous TIE models, instead of two parallel wings to either side of the pilot module, the TIE Defender had three quadanium steel solar array wings 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.[4] The distinctive triple-wing shape of the TIE Defender led Corran Horn to dub them "trips,"[8] and the nickname was also adopted by other Rebel pilots.[4] The wings themselves appeared similar to those found on the TIE Interceptor and TIE Avenger; however, unlike on its predecessors, the wings on the TIE Defender were angled out instead of in.[8] The inclusion of a third wing provided additional solar power to increase the ship's range[1] 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.[9]

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[10] and which was the cause of some frustration among pilots.[1]

Propulsion - The TIE Defender was one of the fastest starfighters in use during the Galactic Civil War.[3] Although it was based on the standard twin ion engine design, it was upgraded to the entirely new,[1] powerful P-sz9.7 twin ion engine, which allowed it a maximum acceleration of 4,220 G and a top speed of 1,680 km/h in an atmosphere—almost 40 percent faster than a standard TIE Fighter.[11] In addition to the main thrusters located in the aft section,[1] the Defender's triple wing design allowed for three arrays of maneuvering jets[7]—which gave it a maneuverability rating of 175 DPF[12]—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[7] and capable of matching the fastest starfighters in the Alliance Fleet.[4]

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

Armament -

The TIE Defender's weapons systems were designed to allow it to engage multiple enemy fighters[3] as well as the armed freighters frequently used by the Alliance.[15] 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.[11] The ion cannons could even be fired simultaneously with the laser cannons.[15] Two targeting sensors were located between each pair of cannons to provide the pilot with a constant stream of targeting information.[1] The ship also featured two M-g-2 general-purpose warhead launchers on the bottom of the pilot module,[7] each of which could be equipped with a standard load of four proton torpedoes or concussion missiles.[4] Depending on the mission profile, the ship could be fitted with alternative warheads such as proton rockets, proton bombs, or magnetic pulse warheads.[9] The inclusion of warhead launchers in the design was considered audacious by some members of the design team.[1]

The small tractor beam projector developed for the TIE Avenger could be easily fitted to the Defender.[9] 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.[4] 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.[8]

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

Systems -

As with other TIE series fighters, the TIE Defender utilized 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 while 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. When not in use, the ship could be left in a password controlled standby mode to prevent unauthorized use.[8]

Various display panels inside the cockpit allowed the pilot to monitor 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, current warhead load and power usage. A chronometer was used to display the mission time,[9] or during hyperspace travel to countdown to reversion to realspace.[8] A heads-up display assisted the pilot in aiming the ship's weapons and displayed data from the ship's threat warning system.[9]

Cost -
File:TIEdefender schem.jpg

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.[1] However, the sophisticated features of the TIE Defender had two major implications. 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.[1] 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.[3] Role==== Template:Quote The design of the TIE Defender offered a starfighter platform with flexibility to outmatch any Imperial starfighter. Statistical data listed the TIE Defender as a space superiority fighter; however, Imperial commanders took advantage of the starfighter's superior abilities to customize mission forces on a case-by-case basis.[3] Defender pilots often found themselves occupying mission roles previously held by older fighters such as TIE Interceptors and Assault Gunboats.[9]

File:TIEdefender negvv.jpg

The TIE Defender's weaponry and deflector shields made it an ideal space superiority fighter, capable of engaging multiple enemies at once.[3] 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.[12]

Equipped with hyperdrive engines, TIE Defenders became well suited for reconnaissance. Standard Imperial doctrine recommended that TIE Defenders operate in flight groups of four, using their hyperdrives to conduct patrols across large areas of space.[3] The versatility of the TIE Defender allowed a large degree of flexibility in its use, as even a single craft could prove formidable,[7] able to outrun or outgun enemy fighters. While on recon 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.[9]

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.[17] 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.[9] Defender squadrons could combine their firepower to eliminate a target as large as Alliance Space Stations, while still covering the starfighter interception role.[18]




Opportunities to train on the TIE Defender were limited, as only TIE Interceptor pilots who had survived at least twenty combat missions were selected; that ensured that only the best pilots flew the advanced starfighter.[11] As with other Imperial starfighters, doctrine required pilots to gain a training certificate by flying the TIE Defender through an enclosed training course before proceeding to combat training 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.[9] Having received a training certificate, Defender pilots could move onto the simulated combat missions, 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.[12] If the pilot successfully completed all four training missions, they received the gold TIE Defender combat medallion.[9]

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.[9]

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 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.[9]


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.[9]

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 escort carriers loaded with starfighters, however the primary objective only dictated the necessity of capturing one carrier. Despite the heavy payload, pilots used their wing mates 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.[9]

By the early years of the Imperial Remnant 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.[8]


Early developmentEdit

Main article: TIE Advanced x7

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.[4] Such was the importance of the TIE Defender that the top secret development project was conducted under the supervision of top naval commanders,[7] including Grand Admiral Demetrius Zaarin, then head of research and development for starfighter technology, and the project would see several prototype stages before its completion shortly before 4 ABY's Battle of Endor.[9]

The initial prototype for the TIE Defender was the TIE Advanced x7, developed at the Sienar Advanced Research Division on Corulag[19] with input from Zaarin.[4] 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;[19] it did not have the final ion engines[4] and lacked the hyperdrive, ion cannons, and missile launchers which were incorporated into later prototypes and the final design.[19]

In early 3 ABY, the Empire launched a massive assault on the Rebel base on Hoth.[20] As the main Rebel forces struggled to delay the Imperials,[4] the Alliance's Renegade Squadron destroyed the weaponry on two Victory II-class frigates[21] 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.[4] However, the early models lacked the speed of the final version and, although they now included missile launchers, the ion cannons were still absent.[21] Six of the TIE Advanced x7 prototypes were destroyed by Renegade Squadron[4] who also managed to board a Star Destroyer and steal one of the fighters to be studied by Alliance High Command.[21] 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's technicians in further developing the fighter.[4]

Final development and testingEdit

Template:Quote 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 which 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.[4] 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[9] and the Empire was planning to roll the finished product out as a replacement for the Assault Gunboat.[22]

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 Sela group 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 but their raiding party was defeated by Imperial fighters.[9]

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.[9]


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.[1] However, 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,[4] leading to some resentment towards the ship, and the commanders that used them in battle.[15] 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.[14] In the end, the field tests were never extensive and this, together with the prohibitive cost, meant that even an organization as wealthy as the Imperial Navy chose not to mass-deploy such a fighter.[1]

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.[23]

Zaarin's betrayalEdit

Template:Quote 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. Though 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.[9]

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.[9]

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.[9]


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 to 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.[9]

However, Zaarin soon sent his own TIE Defenders and assault transports to retake the base. With the AdargaTemplate:'s supply of fighters insufficient to repel the attack and the shields on the research facility not yet at full strength, the Empire was forced to call for reinforcements and deploy one of their few remaining TIE Defenders. Since TIE 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.[9]

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.[9]

In enemy handsEdit

Template:Quote 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.[12]

The Rebels again came close to acquiring the technology as the Mharsup rendezvoused with 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. A Rebel strike team attacked the convoy and attempted to capture it, though it is unclear if they were aware of its valuable cargo. However, Imperial forces were able to hold off the Rebels until the transfer was complete and Hashim group fled to hyperspace.[9]


The Imperials' escape, however, 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. However, the corvettes were still disabled and vulnerable, and the G'nabgib had been captured, giving the pirates access to the TIE Defender scientists. Though 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.[9]

The Empire quickly dispatched three cargo ferries from Mssan group to rescue the prototypes from the stranded corvettes. However, 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.[9]

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. However, 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. Though the Imperial forces succeeded in stopping the Nami from capturing the scientist, the Nami were able to inflict damage on the Red ClawTemplate:'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. However, Zaarin sent his forces, including several TIE Defenders, to distract the Imperial forces, while his own corvette, using Chemeti 1Template:'s transponder code, collected the scientist.[9]


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.[9]

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 to the TIE Defender.[9]

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.[9]

With Tarrak's Deep Space Manufacturing Facility located, Thrawn led the Grey WolfTemplate:'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.[9]

File:D's and MIS's.jpg

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. However, 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.[9]

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.[24]

Other Imperial useEdit


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.[25] 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.[26]

At least one element of TIE Defenders, as part of Onyx Squadron, saw action at the Battle of Endor. However, they were a very small minority of craft at the battle—the majority were TIE Fighters and TIE Interceptors—and were unable to ensure victory for the Empire.[14] 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.[1] Though 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,[16] the cessation of production prevented it from ever achieving widespread use.[1] 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 utilized during the First Battle of Coruscant to defend the Imperial Palace.[27]

Imperial RemnantEdit

Template:Quote 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.[15]

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[16] in the Inner Rim, Expansion Region and Mid Rim[26] aimed at capturing prisoners to serve as his Pawns. Over the course of two months during 5 ABY, 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.[16]

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.[16]

The ship 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[11] and politically unpopular.[15] The few squadrons that remained in service were largely used to patrol the boundaries of what would become the Imperial Remnant.[15]

File:TIE Defender SotG.jpg

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. However, 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 Krennel's 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.[8]

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.[8]

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.[8]

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.[8]

At some point following the establishment of the Imperial Remnant, 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.[28]

Defenders remained in limited use under the Imperial Remnant, deployed in small numbers to the best pilots, rather than to whole 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 the 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. However, 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.[29]

Yuuzhan Vong War and later useEdit


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.[30]

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. Though they eliminated several enemy ships, both TIE Defenders were destroyed helping destroy the Vua'spar to allow Alpha Fleet to escape.[31]

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.[30]

In 44 ABY, 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.[32]

Behind the scenesEdit


A TIE Defender

The TIE Defender was created for the video game Star Wars: TIE Fighter in which the craft was flyable by the player. Although this craft was initially left out of the multiplayer 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!"[33]

There is some discrepancy among sources as to the length of the ship. Recent sources, including the TIE Defender's Databank entry and The Official Starships & Vehicles Collection 67 describe it as 9.2 meters long;[7] however, Star Wars: TIE Fighter had originally given the length as 10 meters, a length which was repeated in The Official Star Wars Fact File 73. Furthermore, both The New Essential Guide to Vehicles and Vessels and More Starships! list the length as 6.6 meters. 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.


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. 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." The figures given in the New Essential Guide to Vehicles and Vessels do 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. The 2007 edition of Starships of the Galaxy describes the TIE Defender as "much faster than any other TIE variant," though it is unclear if this is referring to atmospheric speed or acceleration. Star Wars: Rebellion: Prima's Official Strategy Guide states that "only the A-wing and TIE interceptor are more agile in battle." This contradicts other sources, including the Databank, which state that the TIE Defender was the most agile Imperial starfighter.

Both The Essential Guide to Vehicles and Vessels and the TIE Defender's Databank entry place the cost of the ship at 300,000 credits. More Starships!, however, states that each unit cost 200,000 credits. 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.

TIE Defenders appear in Star Wars Battlefront: Renegade Squadron and fighters which appear to be TIE Defenders can be seen in Star Wars Rebellion 5: My Brother, My Enemy, Part 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. This is similar to the history of the RZ-1 A-wing interceptor, whose pre-Yavin appearances have since been retconned into the R-22 Spearhead. The appearance of the TIE Defender in Renegade Squadron was explained in The Official Starships & Vehicles Collection 67 which established them as early TIE Advanced x7 prototypes.

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 canon source has yet confirmed whether Tyber Zann took this opportunity.

In the 2011 novel Ascension by Christie Golden, the TIE Defender is twice referred to as the "TIE Destroyer."




  • TIE Fighter: The Official Strategy Guide
  • TIE Fighter: Fully Authorized Battle Manual for Imperial Pilots
  • TIE Fighter: Defender of the Empire Campaign Disc: Official Secrets & Solutions
  • TIE Fighter Collector's CD-ROM: The Official Strategy Guide
  • The Essential Guide to Vehicles and Vessels
  • Star Wars Gamemaster Screen, Revised
  • Star Wars: Action Fleet Vehicles (Classic)
  • Star Wars Encyclopedia
  • Star Wars: Rebellion: Prima's Official Strategy Guide
  • Star Wars: X-wing Alliance: Prima's Official Strategy Guide
  • Death Star II Limited
  • Coruscant and the Core Worlds
  • The New Essential Guide to Vehicles and Vessels
  • Star Wars: Empire at War: Forces of Corruption: Prima Official Game Guide
  • Starships of the Galaxy (Saga Edition)
  • Star Wars: The Official Starships & Vehicles Collection 3
  • The Complete Star Wars Encyclopedia
  • Star Wars: The Official Starships & Vehicles Collection 13
  • More Starships!
  • Star Wars Battlefront: Renegade Squadron]
  • Empire at War: Forces of Corruption
  • Message to Spacers 7
  • Star Wars: The Official Starships & Vehicles Collection 67
  • Galactic Civil War 2 – Space: The Ship
  • The Essential Guide to Warfare


  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 Template:FFCite
  2. X-wing: The Official Strategy Guide
  3. Cite error: Invalid <ref> tag; no text was provided for refs named EGVV
  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 4.14 4.15 Star Wars: The Official Starships & Vehicles Collection 67
  5. Template:Journal
  6. Betrayal
  7. Cite error: Invalid <ref> tag; no text was provided for refs named Databank
  8. Cite error: Invalid <ref> tag; no text was provided for refs named Isard.27s_Revenge
  9. Cite error: Invalid <ref> tag; no text was provided for refs named TIE_Fighter
  10. Template:CCG
  11. Cite error: Invalid <ref> tag; no text was provided for refs named NEGVV
  12. Cite error: Invalid <ref> tag; no text was provided for refs named TIE_Guide
  13. Template:CCG
  14. Cite error: Invalid <ref> tag; no text was provided for refs named SotG
  15. Cite error: Invalid <ref> tag; no text was provided for refs named More_Starships.21
  16. 16.0 16.1 16.2 16.3 16.4 16.5 Luke Skywalker and the Shadows of Mindor
  17. Star Wars: Rebellion: Prima's Official Strategy Guide
  18. Star Wars: Empire at War: Forces of Corruption: Prima Official Game Guide
  19. 19.0 19.1 19.2 Coruscant and the Core Worlds
  20. Star Wars Episode V: The Empire Strikes Back
  21. 21.0 21.1 21.2 Star Wars Battlefront: Renegade Squadron
  22. Template:WizardsCite
  23. Star Wars: X-wing Alliance
  24. Star Wars: Empire at War: Forces of Corruption
  25. Star Wars: Imperial Ace
  26. 26.0 26.1 The Essential Guide to Warfare
  27. Star Wars: Galactic Battlegrounds: Clone Campaigns
  28. Cite error: Invalid <ref> tag; no text was provided for refs named SWB:ES
  29. X-wing: Starfighters of Adumar
  30. Cite error: Invalid <ref> tag; no text was provided for refs named The_Unifying_Force
  31. The Final Prophecy
  32. Cite error: Invalid <ref> tag; no text was provided for refs named Ascension
  33. Star Wars: X-wing vs. TIE 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.