Fandom

Wookieepedia

Infiltration of Geonosis Imperial base

134,645pages on
this wiki
Add New Page
Talk2 Share
Queicon

The title of this article is conjectural.

Although this article is based on official information from the Star Wars Legends continuity, the actual name of this subject is pure conjecture.

"We had a Rebel strike team infiltrate an Imperial base on Geonosis. The team was discovered and captured."
―Rahm Kota[src]

During the early Galactic Civil War,[1] at some point between 2 BBY and 0 BBY,[2] the Rebel Alliance attempted to infiltrate an old Imperial droid foundry on the planet Geonosis. The Imperial base possessed strong anti-air defenses. A Rebel strike team was sent to the planet, but due to the team's large numbers, it was soon discovered and captured by the Empire. When the Alliance learned about the mission's failure, they organized a rescue operation to liberate the captured unit. This time, however, the Rebellion took heed of its mistake and dispatched a much smaller force, consisting only of Jedi Master Rahm Kota and the Force-sensitive clone X2. The two of them successfully liberated the prisoners, and the surviving members of the strike team were reorganized into Grey Squadron under X2's command.[1]

Behind the scenesEdit

This mission was alluded to in the Nintendo DS edition of the 2009 video game Star Wars Battlefront: Elite Squadron.

AppearancesEdit

Notes and referencesEdit

  1. 1.00 1.01 1.02 1.03 1.04 1.05 1.06 1.07 1.08 1.09 1.10 Star Wars Battlefront: Elite Squadron (Nintendo DS version)
  2. 2.0 2.1 Star Wars Battlefront: Elite Squadron (Nintendo DS version) shows that the mission occurred at some point between the formation of the Rebel Alliance and the destruction of the first Death Star, which took place in 2 BBY and 0 BBY, respectively, according to the The New Essential Chronology.

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.