FANDOM


This article is about the T-65B X-wing starfighter. You may be looking for the callsign Red Five.

During the Galactic Civil War, at least three X-wing starfighters used by Rebel pilots bore the name Red Five. Cadet Pedrin Gaul operated an X-wing dubbed Red Five in the Battle of Scarif,[13] and also used the corresponding callsign, but was shot down and killed by TIE/ln space superiority starfighters.[14]

Days later, Luke Skywalker and R2-D2 flew a T-65B X-wing starfighter dubbed Red Five in the Battle of Yavin. R2 was damaged by Darth Vader's TIE Advanced x1, but Skywalker used the Force to destroy the Galactic Empire's superweapon, the Death Star.[3] Also his callsign, The Red Five designation became synonymous with the actual spacecraft that Skywalker flew.[15]

Skywalker continued to operate his X-wing until the Battle of Vrogas Vas, when he deliberately collided with Vader in mid-flight to draw the focus of the battle to the planet's surface. Skywalker was rescued by Han Solo in the Millennium Falcon and was forced to abandon his craft.

Ship-stub This article is a stub about a ship or starship. You can help Wookieepedia by expanding it.

Behind the scenesEdit

There are numerous continuity errors within Battle of Yavin scene as depicted in Star Wars: Episode IV A New Hope, many of them introduced by the new computer-generated shots inserted into the The Star Wars Trilogy Special Edition. In the shot of the starfighters flying towards the Death Star, the Red Five has two red stripes on the trailing edge of the S-foils. In some of the subsequent shots, there are 3 or 5 stripes in the same spot. Similar continuity errors are also present in the main line of Star Wars comic books published by Marvel Comics.

AppearancesEdit

Non-canon 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.