Red Squadron (Rebel Alliance)

135,027pages on
this wiki
Add New Page
Talk16 Share
Tab-canon-white  Tab-legends-black 
For other uses, see Red Squadron.
Z-95 Headhunter

Content approaching. Rogue One: A Star Wars Story, The Weapon of a Jedi: A Luke Skywalker Adventure, Star Wars Battlefront, Moving Target: A Princess Leia Adventure and Star Wars 22: The Last Flight of the Harbinger, Part II, Star Wars 25: The Last Flight of the Harbinger, Part V–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.

"Red Group, this is Red Leader."
―Garven Dreis (Red Leader), during the Battle of Yavin[src]

Red Squadron, also referred to as Red Group, was a starfighter squadron of X-wing starfighters that served as part of the Rebel Alliance's starfighter corps during the Galactic Civil War. The squadron participated in campaigns such as the Battle of Scarif, the Battle of Yavin and the Battle of Endor. Following the victory of the rebellion and the reformation of the Republic, Red Squadron was assimilated into the New Republic Starfleet.


Battle of ScarifEdit

"Red and Gold Squadrons, attack formation. Defend the fleet."
―Admrial Raddus giving Red and Gold Squadrons their orders[src]

Red Squadron participated in the Battle of Scarif along with Blue Squadron, Green Squadron, and Gold Squadron under Garven Dreis' command.[13][8] X-wings assisted in engaging Imperial ships above the planet, combating TIE fighters and Imperial Star Destroyers with the rest of the Alliance fleet. During the battle, Pedrin Gaul, flying as Red Five, was killed.[8]


Battle of YavinEdit

"All wings report in. — Red Ten standing by. — Red Seven standing by. — Red Three standing by. — Red Six standing by. — Red Nine standing by. — Red Two standing by. — Red Eleven standing by. — Red Five standing by."
―Red Squadron at the Battle of Yavin — Gnome-speakernotesListen (file info)[src]

Red Squadron participated in the Battle of Yavin under the command of Garven Dreis. X-Wings from Red Squadron made the second and third attack run on the Death Star's thermal exhaust port. Luke Skywalker, flying as Red Five, scored the critical hit during the third attack run, destroying the Death Star.[1]


Chasing after a PrincessEdit

Following the battle, the Alliance decided to evacuate their base on Yavin 4. Princess Leia Organa, along with rebel pilot and fellow Alderaanian Evaan Verlaine, decided to defy the orders of the Rebel leadership and set out on a mission to find and protect surviving Alderaanians from the Empire, The two remaining members of Red Squadron—Skywalker and Antilles-intercepted the shuttle they were in, and ordered them to turn back.[14]

Battle of Vrogas VasEdit

Darth Vader, pursuing his son Luke in the aftermath of the Battle of Yavin, tracked him to the planet Vrogas Vas, where the Rebel Alliance had established a refueling base. He immediately encountered three squadrons of X-Wings, including Red Squadron. Vader destroyed the other two squadrons before colliding with Luke's X-Wing. Father and son both fell to the planet's surface, beginning the Battle of Vrogas Vas.[9]


Battle of EndorEdit

Red Squadron participated in the Battle of Endor under the command of Wedge Antilles. The squadron was composed of a mix of starfighters, including A-wings, X-wings, and Y-wings .[5]


Behind the scenesEdit

In the novelization of A New Hope, Luke Skywalker and Wedge Antilles flew for Blue Squadron. Their squadron was changed to Red Squadron when it was realized that blue markings on the ships would be replaced by moving starfield during blue screen shots. Consequently, the name of the fighter group the novelization called Red Squadron was changed to Gold Squadron for the film.



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.