STAR WARS: Veteran Producer Shares His Take On Why Obi-Wan Kenobi Left Anakin Skywalker Alive On Mustafar

STAR WARS: Veteran Producer Shares His Take On Why Obi-Wan Kenobi Left Anakin Skywalker Alive On Mustafar

Fans have long wondered why Obi-Wan Kenobi didn't make sure Anakin Skywalker was dead after their clash on Mustafar in Revenge of the Sith, and a longtime producer of the Star Wars franchise has chimed in.

By JoshWilding - Feb 17, 2024 01:02 PM EST
Filed Under: Star Wars
Source: Empire (via SFFGazette.com)

When George Lucas set out to make Star Wars, he didn't have some grand nine-movie plan laid out. A New Hope went through countless iterations, as did The Empire Strikes Back and Return of the Jedi; by the time the prequels rolled around, that story was told, and Lucas had to figure out how to tell what came before them. 

There were continuity issues and contradictions (Princess Leia's memory of her mother, for example), but for the most part, The Phantom Menace, Attack of the Clones, and Revenge of the Sith effectively sit alongside the original trilogy. 

The biggest challenge for the filmmaker was taking Anakin Skywalker from the likeable young boy we met on Tatooine to the despicable Sith Lord, Darth Vader. That transformation didn't happen until Episode III's final moments; however, fans have long blamed Obi-Wan Kenobi for the horrors later inflicted by Vader on the Galaxy because he failed to make sure his former Padawan was dead. 

During their lightsaber duel on Mustafar, Kenobi cut off Anakin's arm and legs, leaving him to burn. Emperor Palpatine arrived just in time to save his new apprentice, using the Empire's technology to create more-machine-than-man Darth Vader. 

Talking to Empire (via SFFGazette.com), veteran Star Wars franchise producer Rick McCallum shared his take on why Obi-Wan left Anakin behind without delivering a definitive killing blow as his former ally burned before his eyes.

"I also think he doesn't believe Anakin will recover - he thinks he's going to die," he explains. "It's only because Palpatine comes in and uses everything to save him and create this freak [that he survives]."

Elsewhere in the magazine's feature, Hayden Christensen reflected on being cast as Anakin and admitted he didn't expect to ever land the coveted role.

"I was 18, and I got a call from my agent saying that they were casting for Anakin Skywalker in Star Wars and I thought, 'Wow, how cool.' But it just seemed too big," the actor recalls. "And I remember asking my agent, 'Is there maybe another role that they're also casting right now that you can put me up for? Because Anakin sort of seems unattainable.' And there was not. So I threw my name in the hat like everyone else."

In recent years, we've seen Christensen return to the role of Anakin/Vader in both Obi-Wan Kenobi and Ahsoka. The former explored the emotional and mental toll that the fight on Mustafar had on "Ben," later reuniting the friends-turned-enemies for a confrontation which addressed the apparent plot holes Lucas created. 

As always, be sure to let us know your thoughts on these remarks in the comments section below.

STAR WARS: Henry Cavill Rumored To Have Had Talks About Potential Role In Simon Kinberg Trilogy
Related:

STAR WARS: Henry Cavill Rumored To Have Had Talks About Potential Role In Simon Kinberg Trilogy

STAR WARS Movie - Most Likely Sharmeen Obaid-Chinoy's NEW JEDI ORDER - Pulled From 2026 Release Calendar
Recommended For You:

STAR WARS Movie - Most Likely Sharmeen Obaid-Chinoy's NEW JEDI ORDER - Pulled From 2026 Release Calendar

DISCLAIMER: As a user generated site and platform, ComicBookMovie.com is protected under the DMCA (Digital Millenium Copyright Act) and "Safe Harbor" provisions.

This post was submitted by a user who has agreed to our Terms of Service and Community Guidelines. ComicBookMovie.com will disable users who knowingly commit plagiarism, piracy, trademark or copyright infringement. Please CONTACT US for expeditious removal of copyrighted/trademarked content. CLICK HERE to learn more about our copyright and trademark policies.

Note that ComicBookMovie.com, and/or the user who contributed this post, may earn commissions or revenue through clicks or purchases made through any third-party links contained within the content above.

AC1
AC1 - 2/17/2024, 1:39 PM
Yeah I always felt that, as somewhat selfish in a way that Obi-Wan's decision was to not kill Anakin at that point, it was due to their fight taking too much out of him physically and moreso emotionally - at that point he never thought Anakin would survive but simply didn't have it in him to strike that final blow or to even stay and watch him die. He just couldn't bare to be there any longer at that point.
dracula
dracula - 2/17/2024, 1:59 PM
Another reason is probably its not the jedi way

Anakin said so after killing dooku
EskimoJ
EskimoJ - 2/17/2024, 2:08 PM
Last reason: Because they needed Darth Vader to come into existence.
ProfessorWhy
ProfessorWhy - 2/17/2024, 2:25 PM
He couldn't move and he caught fire. Death would be a fair prognosis
bkmeijer1
bkmeijer1 - 2/17/2024, 6:16 PM
I just guessed it's because Obi-Wan followed certain rules of engagement. Even if it's mercy killing, I don't see him as the bloke to kill an already downed enemy. Same reason he left Vader in his own show.
AnthonyVonGeek
AnthonyVonGeek - 2/17/2024, 9:25 PM
I wish Rick McCallum took over Lucasfilm instead of…

Please log in to post comments.

Don't have an account?
Please Register.

View Recorder