Fandom

Wookieepedia

Obi-Wan Kenobi's second lightsaber

134,565pages on
this wiki
Add New Page
Talk0 Share
Tab-canon-white  Tab-legends-black 
This article is about Obi-Wan Kenobi's second lightsaber. You may be looking for his first lightsaber, or his final lightsaber.
Z-95 Headhunter

Content approaching. Star Wars: Obi-Wan & Anakin–class.

Parts of this article have been identified as no longer being up to date.

Please update the article to reflect recent events, and remove this template when finished.

Obi-Wan Kenobi's second lightsaber was the second lightsaber constructed and wielded by Jedi Knight Obi-Wan Kenobi following the loss of his first one during the battle of Naboo.

DescriptionEdit

Built to replace his first lightsaber,[4] Obi-Wan Kenobi's second lightsaber contained a kyber crystal[3] and emitted a blue plasma blade.[4]

HistoryEdit

ConstructionEdit

Sometime after the Invasion of Naboo, Obi-Wan Kenobi sought to construct a new weapon after he lost his first lightsaber in a duel on Naboo against the Sith Lord Darth Maul.[5]

UsageEdit

Around 29 BBY, Kenobi wielded the weapon during the Mission to Carnelion IV[2]

In 22 BBY, Kenobi wielded the weapon during the unrest of the Separatist Crisis, when he sliced off the hand of the Clawdite Zam Wesell, the bounty hunter assigned to assassinate the Naboo Senator Padmé Amidala, in the Outlander Club, a nightclub located in the underworld of the planet Coruscant. He also wielded the weapon during a skirmish with the bounty hunter Jango Fett on Kamino. Kenobi finally lost the weapon when he was captured by Separatist leader Count Dooku on Geonosis.[1]

Kenobi would later build his third and final lightsaber following his promotion to Jedi Master.[6]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

In other languages

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.