FANDOM


"Controller, an unauthorized droid has just entered the ISB base on Killun 71."
3-9, reporting to Controller LT-319[src]

Killun 71 was a moon occupied by the Galactic Empire in the years leading up to the Galactic Civil War. Its jagged, rocky surface made it difficult to colonize, though the Empire operated an outpost known as Killun Station on one of the rocky protrusions. In an attempt to acquire codes relevant to rebel operations on the planet Lothal, the rebel cell known as Phoenix Squadron infiltrated the outpost, stealing sensitive information from the Empire.

DescriptionEdit

Killun 71 was a moon located near a larger, white celestial body.[2] The moon had a green appearance from space; this was due to an omnipresent layer of mist in its atmosphere. Its terrain was composed of large, rocky protrusions and jagged landmasses that made colonization difficult.[1]

HistoryEdit

"I will alert the station at once."
"No, we'll inform the ISB after I have what I need from that spy."
―3-9 and Controller LT-319 discover Chopper infiltrating Killun Station[src]
KillunStation

The Imperial base Killun Station sat on one of the moon's jagged landmasses prior to the Galactic Civil War.

Despite the moon's large, jagged rocks, the Galactic Empire maintained an outpost on Killun 71 known as Killun Station. Established and operated by the Imperial Security Bureau,[1] Killun Station contained sensitive data and orbital clearance codes for the planet Lothal, making the base a prime target for the rebel cell known as Phoenix Squadron, which was planning an upcoming attack on Lothal.[2]

Around 2 BBY,[3] Phoenix Squadron agents Wedge Antilles and the droids C1-10P and AP-5 infiltrated Killun Station to recover the Lothal codes. Although Chopper was compromised by Imperial Information Office[2] Controller LT-319,[4] the two droids were ultimately successful in their mission.[2]

LocationsEdit

"Halt. Proceed through the scanner one at a time."
―An Imperial stormtrooper enforces Killun Station's tight security measures[src]

One of Killun 71's jagged landmasses was home to Killun Station, an outpost operated by humans and droids[2] of the Imperial Security Bureau. Due to the sensitive nature of the data stored in the base, security was especially tight. Stormtroopers were stationed at every entrance, and the base was equipped with walkthrough identification scanners.[5]

Behind the scenesEdit

Killun 71 concept art

Concept art of Killun 71 for "Double Agent Droid"

Killun 71 made its first appearance[2] in the nineteenth episode of season three of the Disney XD animation television series Star Wars Rebels.[6] The episode, titled "Double Agent Droid," aired on March 11, 2017.[7]

AppearancesEdit

SourcesEdit

Notes and referencesEdit

Wiki-shrinkable
Wookieepedia has 6 images related to Killun 71.
  1. 1.0 1.1 1.2 StarWars-DatabankII Killun 71 in the Databank (backup link)
  2. 2.0 2.1 2.2 2.3 2.4 2.5 2.6 2.7 2.8 2.9 Rebels-mini-logo Star Wars Rebels – "Double Agent Droid"
  3. TwitterLogo @pablohidalgo (Pablo Hidalgo) on Twitter. "six months pass between the S2 finale and the S3 premiere. We're about 2 years from Ep4" (screenshot)Pablo Hidalgo of the Lucasfilm Story Group states that Star Wars Rebels Season Three begins "about 2 years" before the events of Star Wars: Episode IV A New Hope, or 2 BBY, according to Star Wars: Galactic Atlas, thereby providing an approximate date for the events of the Season Three episode "Double Agent Droid."
  4. StarWars-DatabankII Controller LT-319 in the Databank (backup link)
  5. StarWars-DatabankII Killun Station in the Databank (backup link)
  6. SWCustom-2011 Double Agent Droid Episode Guide on StarWars.com (backup link)
  7. Star Wars Rebels - Season 3, Episode 18: Double Agent Droid. TV.com. CBS Interactive Inc. (2017). Archived from the original on September 7, 2017. Retrieved on September 7, 2017.
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.