FANDOM


Tab-canon-white  Tab-legends-black 

The Flitknot Speeder Bike,[3] also known as the Flitknot Speeder,[1] Geonosian Speeder,[4] or the Separatist speeder,[5] was a model of speeder bike used by the Confederacy of Independent Systems.[1]

CharacteristicsEdit

The Flitknot Speeder was the preferred speeder bike of the Sith Lord Count Dooku. These bikes are fast and maneuverable, enough so that it is able to outrun a Galactic Republic gunship. Being of simple design, this speeder has more bulk located at its rear in the engines than anywhere else. It has dual handholds and dual footholds, making them ideal for humanoids to use.[1]

HistoryEdit

Count-dookus-speeder 099a9e27

Count Dooku riding his speeder.

Count Dooku used a Flitknot during the First Battle of Geonosis to escape from the Stalgasin hive to his secret hangar. He abandoned the vehicle once he left Geonosis in his solar sailer.[2] Dooku also rode a Flitknot speeder to meet Anakin Skywalker and duel him on Tatooine. Following the duel, Skywalker stole the speeder to escape the Dune Sea and head for Jabba the Hutt's Palace.[6]

STAPs BSV

Three B1 battle droids riding STAPs escort a tactical droid riding a Flitknot speeder.

At least one Flitknot speeder, painted in the Separatist color scheme, was used by a tactical droid to patrol Naboo prior to the Blue Shadow Virus incident.[5]

During the Second Battle of Geonosis, Flitknot speeders were extensively used by the Geonosians.[7] Many Commando droids used Flitknot speeders during the Battle of Kiros.[8] Clone troopers used captured speeders to go to places on Coruscant. One was used by clone trooper Fives when he was trying to escape from other clones to prove his innocence when he was framed for the attempted murder of Supreme Chancellor Sheev Palpatine.[9]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

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.