Fandom

Wookieepedia

Mace Windu's TX-130 Saber-class fighter tank

English

Mace Windu's TX-130 Saber-class fighter tank

134,625pages on
this wiki
Add New Page
Talk0 Share
Queicon

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.

This customized, purple-colored TX-130 Saber-class fighter tank—also called a Jedi fighter tank—was a maneuverable, fast-attack hovertank used by High Jedi General Mace Windu during the Clone Wars.

CharacteristicsEdit

High Jedi General Mace Windu piloted a TX-130 Saber-class fighter tank marked with the Jedi's characteristic purple colors. Though Republic fighter tanks were generally manned by a clone trooper pilot, copilot and gunner, the speed and maneuverability of Mace Windu's tank responded well to the Force-enhanced skills of the Jedi Master without the assistance additional clone crew members.

Armed with a turret mounted laser cannon and dual heavy cannons that can fire concussion missiles, the tank was further modified with an onboard R2-series astromech droid, as well as greater shield power than most other fighter tanks were equipped with.

HistoryEdit

During the First Battle of Geonosis, three Dark Acolytes attacked Mace Windu's fighter tank while he made his way to Count Dooku's hangar to confront the Sith Lord. They dealt heavy damage to his tank, but he managed to penetrate their shields, overpowering and destroying them.

The tank was later used during the Battle of Thule, when Mace Windu commanded ground forces around Thule's capital city of Kessiak. A Dreadnought battle tank piloted by Cydon Prax then arrived, destroying the Jedi fighter tank and forcing Windu to travel on foot to complete his mission.

AppearancesEdit

SourcesEdit

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.