FANDOM


File:SlaveI.jpg

Slave I is a fictional spacecraft in the George Lucas's science fiction saga Star Wars. It is used by bounty hunter Jango Fett and his son Boba Fett. Jango Fett acquired this vessel while on a mission to locate Komari Vosa; this was the mission organized by Darth Tyranus to find the best candidate to be cloned to form a clone army. He used this ship to escape an exploding prison on an asteroid after his own ship was destroyed. Nobody ever searched for this ship as being missing from the prison as it was believed to be destroyed in the explosion of the prison. Slave I appears in the films Star Wars Episode II: Attack of the Clones and Star Wars Episode V: The Empire Strikes Back.

In the Star Wars canon, Jango Fett is the first acknowledged owner of Slave I. In Attack of the Clones, Jango flies the ship to Geonosis, where he dies in combat with Mace Windu. In The Empire Strikes Back, we find that Boba Fett has acquired Slave I in the interim.

In The Empire Strikes Back, Boba Fett uses the vessel, which is outfitted to contain prisoners, to deliver Han Solo to Jabba the Hutt after Darth Vader freezes Solo in carbonite.

While docked and during takeoff and landing, Slave I is oriented horizontally; but in flight, its wing pylons rotate 90°, perpendicular to the attitude of the ship, and the ship is propelled while oriented vertically. Two-thirds of the ships interior is dedicated to the powerful Kuat Engineering Systems F-31 drive engines and the four Kuat X-f-16 power generators, giving the ship the speed of an Alliance Y-wing fighter.

Both Jango and Boba Fett modified and rearmed Slave I. Under Jango Fett's ownership, its weaponry included twin blaster cannons, two rapid-firing laser cannons, two projectile launchers (each equipped with a magazine of three proton torpedoes or various other payloads), and a naval mine-layer equipped with three seismic charges, weapons powerful enough to easily bisect asteroids with a radius of five to ten kilometers. In addition to combat-grade shields and sensors, Slave I has an illegal sensor masking and jamming system that allows it to slip through sensor grids undetected. This system, thought to be an Imperial navy Military secret, was somehow acquired by Fett and has given him a decisive advantage on many hunts. He can use the system to sneak onto worlds undeteced, much to the dismay of his targets and planetary law-enforcement. Slave I has dummy proton torpedoes mounted with homing beacons and S-thread trackers. By taging a ship with one of these dummy beacons, Fett can use his contraband HoloNet transceiver to track ships through hyperspace. In other words, once he has found you, it is almost impossible to dodge the infamous Boba Fett.

Slave I in the Expanded Universe

The Star Wars Expanded Universe reveals more of the history of Slave I:

  • Kuat Drive Yards specially designed the ship to carry live prisoners. Slave I was one of six prototype Firespray-class patrol and attack ships manufactured for the asteroid prison Oovo IV. While on Oovo IV, Jango Fett stole a Firespray and proceeded to destroy the rest. Kuat revived the line around the Battle of Yavin.
  • After Boba Fett assumed control of the vessel, he replaced the laser cannons with an ion cannon and a concussion missile launcher, and also added a tractor beam.
  • Boba escapes from the Great Pit of Carkoon and discovers that Slave I has been impounded, forcing him to rely on a Slave II model until he recovers his ship.
  • In The Bounty Hunter Wars, Boba Fett states he had Kuat Drive Yards build the ship to his specifications, and he went over the ship with a fine tooth comb upon receiving it. He then made various adjustments and changes as he deemed fit. This series was written prior to the movie prequels though, hence the story about Jango mentioned above.

References

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.